|Subject:||Re: Add Version/Date When Checking In File|
|Date:||Fri, 19 Jan 2007 09:57:43 -0600|
Aaron Bono wrote:
> On 1/18/07, Robert Clark <address@hidden> wrote:
>> On Thursday January 18, 2007 11:57, "Aaron Bono" < address@hidden>
>> > We want to add the CVS version of a file, a time stamp of when the
>> > file is checked in and the user who checked the file in to all
>> > source code files.
>> Just out of morbid curiosity: why would you want to do such a thing?
>> All that information is already stored in the repository by CVS when
>> you commit the file.
> It helps when tracing back a file from production to it's source. Once the
> files are checked out and bundled for deployment, there is no other way to
> tell what version of each file we are using on the production box without
> doing some detective work.
You might also be able to get what you need by one of the following methods:
A) When bundling for deployment, also run `cvs2cl -r -t` in the base
directory of the checkout and use one ChangeLog for the whole of the package.
B) When bundling for deployment, also run `cvs2cl -r -t -d` in the base
directory of the checkout so you have a ChangeLog for the files in each
directory in the directory where those files are.
C) When bundling for deployment, have a build target that runs `cvs2cl -r -t
-f filename.cl filename` for each file, so that you ChangeLog for each
If you release from branches the '-F branchname --no-ancestors' options might
You also may wish to use the RCS keyword $Id:$ so that folks can match the
version of each file they received with the versions listed in the ChangeLog.
following thread may be of interest to you as well:
If you happen to be running a version of CVSNT, there is a cvs2cl.py which
at least at one time took the same options and gave similar results to the
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
|[Prev in Thread]||Current Thread||[Next in Thread]|