Milind Pande wrote: > > I am working to write some auditing scripts for identifying objects checked > out for more than 30 days. The problem I am facing is, I am not getting the > checked out date. I had a look at history file but could not get anything. > Can anyone help me in achieving this. >
Why would you care? I for one have baselines still checked out from a year or two ago. If you do a checkout and then repeated updates, the files which were correct out of the starting blocks would look like they might have been checked out for the life of the project. Or are you one of those who uses file locking/reserved checkouts/watches(to encourage cvs edit&unedit)? If so why? With Concurrent Versions System (CVS) each person on the team can have the source file checked out at one time and allow all of the team to change it at one time (or not if they have no need), with the only modulo to that being unmergeable files (binary or some "beautified"). So I at least have a hard time seeing why to waste time making such an audit script. But if you insist, have a look at the response I gave to Cheung Chun Kui yesterday. https://www.cvshome.org/docs/manual/cvs-1.11.18/cvs_8.html#SEC75 https://www.cvshome.org/docs/manual/cvs-1.11.18/cvs_16.html#SEC138 cvs history -o cvs history -xU > Regards, > Milind > http://mailformat.dan.info/trailers/disclaimers.html <The email being replied to was sent _to_ a _public_ email list, so the Stupid (but at least short) Email Disclaimer removed. Please help your boss get oxygen to the brain.> -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
