--- Kaz Kylheku <[EMAIL PROTECTED]> wrote: > On Mon, 26 Aug 2002, Noel Yap wrote: > > > I'm not sure if this is a known problem (or even > if > > it's recognized as being a feature rather than a > bug) > > but here it goes: > > "cvs annotate" does not use sticky tag. One > would > > have to use the "-r" option in order to annotate a > > particular version. > > Using the sticky tag would be unsatisfactory in the > case that it's a > branch tag, because you would be annotating from the > branch tip. > > In the absence of an overriding date or revision > spec, cvs annotate should > just use the closest repository version number from > CVS/Entries. If > you are working with 1.8, with no sticky tag, and in > the meanwhile 1.9 > and 1.10 have been committed, you probably aren't > interested in the > inclusion of these latest revisions when you run cvs > annotate; you don't > even know that they exist unless you update, or > inspect the cvs log. > You want to know who previously touched some line of > code in revision > 1.8 or earlier, not who is going to do it in > revisions that are, to you, > still future revisions.
I don't understand. Currently (from what I'm seeing), "cvs ann" will annotate the head revision on the trunk, regardless of the working revision. Unless our definitions of "Sticky Tag" differ, it sounds like we agree on what "cvs ann" /should/ do. Noel __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
