Re: What's remembered? "S" flag suggestion

[Eric Siegerman]

On Wed, Aug 08, 2001 at 10:42:57AM -0400, Derek R. Price wrote:
> Kent Henneuse wrote:
> 
> > Eric Siegerman wrote:
> > > If there's a sticky release tag on a file, cvs should tell me.
> > > How about a new status code from "update":
> > >         S foo.c
> >
> > This would be fantastic.  I would think that cvs would only
> > show you sticky revisions and not things like branches.  For the
> > branch case cvs could just print out a line at the begining or
> > better yet the end of a cvs update saying "In branch tag XYZ".
> 
> I don't think so.  For the simple reason that an update of any full
> checkout with a tag, branch or not, would list every file.

Branch tags:  no it wouldn't; we've specified that this NOT
happen.  Non-branch tags: why isn't that desired?  If I do a "cvs
update" (neither -r nor -A) in a sandbox checked out with a
sticky release tag, surely I want to be told -- loudly -- that
nothing's gonna happen.

> I think most
> users aren't going to be happy with that.

If it happened with branch tags, I agree!  Which is why the
proposal explicitly says that it not happen with branch tags.

Maybe I should clarify; I interpret Kent's suggestion for an "In
branch tag XYZ" message to mean once per update, or at most once
per directory, perhaps as an addendum to the existing "cvs:
Updating ..." message -- NOT once per file like "file foo.c was
lost" warnings.  And in any case, that's a separate proposal,
independent of and orthogonal to the "S foo.c" proposal.  The two
should not be conflated.

> So if it is going to be a matter or requesting the output anyhow, the
> information is already available via the status command.  I might be
> behind a --brief option to status, or the like, if someone else did the
> work.

"status --brief" would be nice -- very nice, in fact.  I can't
think, though, what else it should be if not a synonym for
"cvs -n[q?] update".  So we're back to square one :-)

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
        - RFC 1925 (quoting an unnamed source)