[Top][All Lists]

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

RE: CVS history query

From: Mark Priest
Subject: RE: CVS history query
Date: Thu, 20 Oct 2005 20:27:31 -0400


Have you tried using the history command?  If the history file was created
with the right permissions in the repository (and no exclusions were
specified in the repository config file) you should be able to use the
history command to find out what cvs commands were issued from each user and
the associated file location in the working directory.  This should tell you
what you want to know.  

To show all events (including updates) for user joe you would execute 

cvs history -e -u joe 


-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Jason Brown
Sent: Thursday, October 20, 2005 8:10 PM
To: address@hidden
Subject: CVS history query

Greetings all, been lurking for several months trying to get up to speed
beyond reading the manuals, but have a question regarding an incident that
recently occurred...

Is there any way in CVS to get a "working copy history"...e.g. some
compilation or options that can be tweaked to view what commands people have
ran from a checked out copy?  

We have a system where a file appears to have been rolled back to a previous
version (1.33 of 1.46) sometime in the past day--but bash history, and
searching for local backup copies (.#foo.file) reveals no evidence of any
commands (or even file modifications on this it is just a
testbed where files are checked out and ran) other than a boring "cvs
update" and the recent creation of a tag "cvs tag stable_2005_10_20"

Whatever happened did most certainly set the file in question to sticky, as
it required resetting the tags (cvs update -A filename) to get an update on
it to take.  

Any theories...or ideally someone telling me there's some way configure CVS
to track or log working copy history would be appreciated.


Info-cvs mailing list

reply via email to

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