Thanks for the suggestion. This is kind of what I am doing at the moment, but an autogenerated PDF report I can stick under my bosses nose would demonstrate that nothing is getting missed.
As a fallback, I am writing my own custom script that is writing every commit message into a mysql database (actually the bugzilla one!) so I can query the information myself. I've not really got this working - has anyone else tried something similar Robert. -----Original Message----- From: Kristis Makris [mailto:[EMAIL PROTECTED] Sent: 14 November 2006 18:04 To: Robert G Ward Cc: [email protected] Subject: Re: [scmbug-users] failure to run vdd generator On Mon, 2006-11-06 at 09:38 +0000, Robert G Ward wrote: > I am trying to run the VDD generator, and am getting an error. > > Using Scmbug RELEASE_0-17-1 > > Is there a simple way to get this working? There is another way to get this working for CVS. Since we now report the branch name in commit messages, one could harvest from the buglist the changes by inspecting the comments (of all bugs in the product; this makes the process slower, but still doable) themselves to find a matching branch name. _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
