Re: CVS and tracability

2005-03-06 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Familie Moner [EMAIL PROTECTED] writes: I'm faced with the requirement to trace changes due to certain bugfixes, i.e. to answer questions like which files have been affected by change request 1234. Currently, the only way I can think of to

RE: CVS and tracability

2005-03-06 Thread Arthur Barrett
/support.cvsnt Regards, Arthur Barrett -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Familie Moßner Sent: Sunday, 6 March 2005 10:06 PM To: info-cvs@gnu.org Subject: CVS and tracability Hi, I'm faced with the requirement to trace

Re: CVS and tracability

2005-03-06 Thread Paul Sander
You can also use rcsinfo to prompt the user for a defect ID and use loginfo to record the modified files and version numbers in your defect tracking system. Done right, you also get the ability to query for bugs fixed in a given build. On Mar 6, 2005, at 3:06 AM, [EMAIL PROTECTED] wrote: I'm

Re: CVS and tracability

2005-03-06 Thread Steve McIntyre
On Sun, Mar 06, 2005 at 02:10:07PM -0800, Paul Sander wrote: You can also use rcsinfo to prompt the user for a defect ID and use loginfo to record the modified files and version numbers in your defect tracking system. Done right, you also get the ability to query for bugs fixed in a given