-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
Thanks to all for comments and suggestions!
On Thu, Mar 03, 2005 at 05:50:02PM -0500, Greg A. Woods wrote:
Do not use cvs import. It can not work as any part of what you want
to do.
Hmm, Cederqvist recommends it in
https://www.cvshome.org/docs/manual/cvs-1.12.11/cvs_13.html#SEC108
On Fri, Mar 04, 2005 at 02:42:56AM +, Pierre Asselin wrote:
Greg A. Woods [EMAIL PROTECTED] wrote:
Multiple vendor branches CANNOT work for what you want. Period.
Maybe with the new import -X in cvs 1.12.x ? This was touched
upon briefly in another thread.
Thanks for the link, I'll
On Fri, Mar 04, 2005 at 11:38:09AM -0500, Larry Jones wrote:
Baurzhan Ismagulov writes:
1. Added and deleted files: I have to track them manually when I apply
the delta for a new upstream release. I have to grep for 1970 and add
/ remove the files.
That shouldn't be necessary --
CVSNT (also GPL, free, Windows, Linux, Unix, Mac etc) has a -B bug switch for
cvs edit, cvs commit etc etc. This can be captured by the various triggers
so that each time a commit is done the information is available. You can
either log the info there, or integrate it directly with your
Baurzhan Ismagulov [EMAIL PROTECTED] wrote:
On Fri, Mar 04, 2005 at 02:42:56AM +, Pierre Asselin wrote:
The multiple vendor branch was not funny, so I agree with Greg.
I had to manually reset many admin -b values, move files in and
out of the Attic (I think), etc. When I got to the
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
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
Title: changing the encoding - file is corrupted
Hi,
I have a .xsl (text) file which had few revisions (added with wincvs) with UTF-8 encoding-format. Now when I have converted that file to UTF-16 encoding with XML spy editor - this file is getting corrupt after adding the same - specially
