cvs help

Scott Prive scottprive at earthlink.net
Thu Jun 26 11:16:49 EDT 2003


It's mission impossible to give the answer I think he wants by end of day.

It sounds like your manager does not understand the purpose of CVS -- to version files.

Now, you can do commands like cvs history, etc. but these are not "reports". Given a budget, you could program Perl or shell scripts for getting this information out of CVS and save it out in a manager-friendly format. 

There *may* be some canned scripts in the Bugzilla or Mozilla opensource projects, but very likely these require some development work for your purposes. 

Alternatively, you might find commercial packages that do this. I'm not aware of any, but I never looked. 

Good luck,

Scott



-------Original Message-------
From: Frank Ramsay <fjramsay1234 at hotmail.com>
Sent: 06/26/03 12:37 PM
To: discuss at blu.org
Subject: cvs help

> 
> I've just been given the task of setting up CVS here at the office, but
then 
the phb who made the descision descides he want to know how to generate
all 
sorts of automated reports of the code:
vesion history, file history, branch history, and more complex stuff like 
version X of our software is made up of these versions of these files...
Now I don't know much about cvs, I've done a few co's from wine and that's 

about it.  But I figure I can get it set up and running easily enough, but 

how do I generate these reports?   Oh, and did I mention he want's 
documentation of how to do all this, by the end of the day?  so if anyone 
has any ideas please let me know.

Oh, and is there an AS/400 cvs client that anyone knows of?

                                                                      -fjr

Frank J. Ramsay
fjramsay1234 at hotmail.com

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail

_______________________________________________
Discuss mailing list
Discuss at blu.org
http://www.blu.org/mailman/listinfo/discuss
> 



More information about the Discuss mailing list