CVS gurus:
I have written a script (Perl) that is called via
the "notify" administrative file and it works great,
but I would like to include the new *version number*
of the file that was just committed in the notification
message that gets sent out. As far as I can see in
the CVS documentation
Aldo Longhi wrote:
> As far as I can see in
> the CVS documentation (Cederqvist), this information
> is NOT passed to the "notify" script by CVS (as it is
> for other "trigger" operations).
Actually, the new revision number is only passed to loginfo. Everything
else (commitinfo, verifymsg) suffe
So who knows how can I find the version number that
was MOST RECENTLY checked in (regardless of branch)
for a particular file by a particular user? Here's
the "cvs history" command that I have so far:
"cvs history -c -a -l -f "
The problem I encountered when testing this is that
I got more than
Aldo Longhi writes:
>
> It would appear that CVS is doing some sort of "grep" on the
> history file and listing all files in this directory that
> START with the filename I gave.
It's even worse than that -- history lists any files that *contain* the
given filename. For example, if you give a f
