info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs log between tags


From: Laine Stump
Subject: Re: cvs log between tags
Date: 06 May 2001 16:05:40 -0400
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

address@hidden (Greg A. Woods) writes:

> [ On Saturday, May 5, 2001 at 19:51:00 (-0400), Larry Jones wrote: ]
> > 
> > cvs -H log says, in part:
> > 
> >         -r[revisions]   Specify revision(s)s to list.
> >            rev1:rev2   Between rev1 and rev2, including rev1 and rev2.
> >            rev1::rev2  Between rev1 and rev2, excluding rev1 and rev2.
> > 
> > I think :: was new in CVS 1.11.1.
> 
> Unfortunately neither are useful for the most common case I want to use
> (which I suspect is what Jim wants too).
> 
> I want to find all the log entries between releases, which to me means
> after the first tag and up until and including the second one.  In other
> words I need:
> 
>       Between rev1 and rev2, excluding rev1 and including rev2.
> 
> Seeing that last log entry is just as important as not seeing the first
> one.

Good point. I want (through *some* method) exactly the same
functionality as you, and I imagine many others do too. I had
suggested implementing the "::" syntax for log because ":" was already
there for log and admin, "::" was already supported for the admin
command to mean "exclusive of the first and last revisions", and my
feeble mind was at the time thinking something along the lines of
"since the tag happens *after* the last revision is committed, that
last revision will be included in the logs". Of course that thinking
is flawed... (I hadn't yet noticed, because I was waiting for it to be
in an official release before doing anything with it.)


So is there an actual use for a command that excludes that last
revision from the log? Since this is a newly implemented option, maybe
the meaning can be changed slightly to mean "only revisions that were
committed after the first tag, and prior to the last". Since the
revision with the same number as the last tag was, by definition,
committed prior to making the tag, this would give us what we want
(ie, it would include that last revision), and wouldn't skew the
meaning *too much* from what it means elsewhere ;-)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]