[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: bug / enhancement regarding cvs log
From: |
Navin Daryanani |
Subject: |
RE: bug / enhancement regarding cvs log |
Date: |
Mon, 22 Oct 2001 14:38:00 +1000 |
Sorry I don't mean to bug anybody - but I just checked out a version of ccvs
and tried to build it from sources and wanted to checkout the feature I
needed. I don't seem to get the right results. I mean when I do a log of a
range of revisions I still get a log of a ver old file which was not
modified in that revision range.
I tried looking thru the sources to see if I can quickly see if there is an
option or something else - but couldn't locate it. Can you pls tell me what
option do I have to use (If you are aware of it).
FYI: Currently I am solving my problem by a small perl script I wrote which
does a cvs history and greps all commits and then builds a file(s) list -
which I pass to the cvs log command eventually. It is not a very clean
method bec' the history command's options on revision tag and log command's
revision tags are different. So I was just hoping if I could find an
alternative soln. Maybe start working on it too - if it has not been started
yet :-)
thanks & regards
navin
-----Original Message-----
From: Larry Jones [mailto:larry.jones@sdrc.com]
Sent: Saturday, 20 October 2001 3:53 AM
To: Navin Daryanani
Cc: bug-cvs@gnu.org
Subject: Re: bug / enhancement regarding cvs log
Navin Daryanani writes:
>
> Consider a command 'cvs log -rMod13:Mod15'
>
> This command does not filter out (and there are no options as far as I can
> see) the files which have not been modified in this tag ranges. It would
be
> nice to have a log on files modified in this tag range only. This way we
can
> see exactly which files have changed and with what log messages.
I believe this is fixed in the current development version of CVS.
-Larry Jones
Oh, now don't YOU start on me. -- Calvin