info-cvs
[Top][All Lists]
Advanced

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

RE: history command


From: Thorsten Schacht
Subject: RE: history command
Date: Wed, 20 Apr 2005 09:42:50 +0200

Ins't 
# cvs history -c -a
what you need? The -c shows only the commits instead of -e that shows
all.

-a means every user. Use -u user to limit the output.

http://computing.ee.ethz.ch/sepp/cvs-1.10-to/cvsbook/main_80.html 

Thorsten

-----Original Message-----
From: Todd Denniston [mailto:address@hidden 
Sent: Dienstag, 19. April 2005 17:53
To: dave frost
Cc: address@hidden
Subject: Re: history command

Larry Jones wrote:
> 
> dave frost writes:
> >
> > Could anyone tell me how to get user commit comments in the
> >
> > cvs history -e -a
> >
> > output ?
> 
> Only by rewriting CVS.
> 
> -Larry Jones
> 
Or by re-writing your question to ask how to get the information you
need,
not how to make a command do something it was not meant to do.
i.e. what out of `cvs history -e -a` do you actually need, to go along
with
the output from `cvs log`?
I rarely, i.e., NEVER, find the information in cvs history to be of use,
except when trying to rebuild a repository from the remains of a failed
raid
0 array (been there done that, better backups now), however the output
of
`cvs log` as parsed by the script cvs2cl [1] is something I use almost
daily. If you still want the output of `cvs history -e -a` combined with
the
output of `cvs log` then look at cvs2cl and see about writing a
script||program to do the combination for you.

[1] http://www.red-bean.com/cvs2cl/
-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter


_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/info-cvs





reply via email to

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