Re: Logs between releases

[Greg A. Woods]

[ On Monday, April 8, 2002 at 16:32:24 (-0400), Larry Jones wrote: ]
> Subject: Re: Logs between releases
>
> Kaz Kylheku writes:
> > 
> > On Wed, 3 Apr 2002, Valerio Ferrucci wrote:
> > > 
> > > Which is the best way to obtain the logs for all files changed 
> > > between two release?
> > 
> > cvs log -r rel-tag-n -r rel-tag-n+1
> 
> That only gives you the log messages for those two specific revisions,
> not all the log messages for changes between the two tags.  The way to
> do it is to download the current development version of CVS and then do:
> 
>       cvs log -rrel-tag-n::rel-tag-n+1
> 
> (Some versions of CVS prior to the current development version will
> accept that syntax, but they'll include the log message from rel-tag-n
> in the output which you don't really want.)

We do normally want the the log message for rel-tag-n+1 if, but only if,
it's on a different revision from rel-tag-n; and that's not how the
current development version works, yet.  (This is not the same as also
adding '-rrel-tag-n+1' to the command!)

The 'rev::' variant is close to this, but of course only until any new
revision is committed after a release is made....


It would also be very nice if there were an option flag to cause nothing
at all to be printed about a file when no revisions are selected.

It would also be very nice if there were an option flag to ommit all of
the header except the working directory file name, relative to the
directory from where cvs is invoked (or in the case of 'rlog' relative
to the base of the module directory in the repository, but without the ,v).

-- 
                                                                Greg A. Woods

+1 416 218-0098;  <address@hidden>;  <address@hidden>;  <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>