Re: bug / enhancement regarding cvs log

[Larry Jones]

Navin Daryanani writes:
> 
> current status of the repository module : WSA/iCare - everything commited
> and in sync and the latest version tagged with iCare060
> 
> modified Application.java - say for e.g., added a line break at the
> beginning of the file
> 
> "cvs commit Application.java" <and gave a log : cvs testing>
> 
> "cvs rtag dev2310 WSA/iCare "
> 
> when you do a "cvs log -rdev2310 -wnavin " you get the foll. output. (For
> brevity I have kept the log of the first 3-4 files only.)

Which is exactly what you should expect.  Note that -r and -w do not
specify which *files* to log, they specify which *revisions* to log. 
So, you should expect a header for every file, but only files that meet
the specifications will have "selected revisions" greater than zero.  In
this case, you're asking for all revisions that have the tag dev2310
that were checked in by navin, which isn't even close to what you want
since there's no requirement that that revision be different from the
revision identified by any other tag.

> Notice that I had modified only Application.java in the revision tag dev2310
> and I got many more files which weren't even modified in this tag - and I get 
> the same output
> even if I do "cvs log -riCare060::".

It doesn't make sense to talk about files being modified "in" a tag --
tags just mark revisions.  The only sensible thing to talk about is
files modified *between* two different tags.  Asking for revisions after
iCare060 is what you want, I think; files with "selected revisions"
greater than zero should be exactly those files that were modified after
that tag was applied.  You could also do something like
-riCare060:dev2310 and look for files with more than one selected
revision.

-Larry Jones

In short, open revolt and exile is the only hope for change? -- Calvin