info-cvs archive search

121. Q re commitinfo modifying the file being committed (score: 11)

Author: HIDDEN

Date: Wed, 9 May 2001 15:59:04 -0500

I have a commitinfo script whose job is to modify certain files on their way into the repository. (One might think of it as incrementing a version string that's in the code, kind of like how RCS keyw

/archive/html/info-cvs/2001-05/msg00323.html (4,566 bytes)

122. Re: $Name $ in branches (score: 11)

Author: HIDDEN

Date: Sat, 21 Apr 2001 02:32:06 -0400 (EDT)

[ On Friday, April 20, 2001 at 08:49:34 (-0500), David D. Hagood wrote: ] Hmmm... sounds like you've also got some "confusion" between branches and modules. If that's a real example, why would UI and

/archive/html/info-cvs/2001-04/msg00555.html (13,284 bytes)

123. RE: Verifymsg on branches? (score: 11)

Author: HIDDEN

Date: Wed, 22 Nov 2000 13:29:27 -0600

Uwe, I've just finished my first cut at doing per-branch bug number requirements in our CVS repository. Bear in mind I haven't finished testing it yet, so I could be way off base here. It also presum

/archive/html/info-cvs/2000-11/msg00318.html (12,455 bytes)

124. Re: Verifymsg on branches? (score: 11)

Author: HIDDEN

Date: Mon, 20 Nov 2000 17:37:53 -0800

Laird, Thanks for your answer. My idea was to have a different log template for the trunk as compared to the branch. As this seems not possible, I now think it would be enough to add the BugID line t

/archive/html/info-cvs/2000-11/msg00280.html (8,033 bytes)

125. Re: Verifymsg on branches? (score: 11)

Author: HIDDEN

Date: Tue, 14 Nov 2000 10:03:16 -0500

Well, you can't really do this (yes, you SHOULD be able to). This is due to two major things: 1. You cannot get the new version number of a file being committed. So you'll never know if that file is

/archive/html/info-cvs/2000-11/msg00206.html (6,345 bytes)