Hack/Work Around for Log Message Templates?
From: Brian Huddleston <brianh_at_huddleston.net>
Date: 2005-04-14 07:32:20 CEST
Hi guys,
Some advice if you would be so kind.
Background:
I'm hoping to move our dev organization over to Subversion sometime in the fairly short term. I finally got a successfull cvs2svn after editing a few hundred RCS file that were boogered in various ways and was happy happy happy. I was actually typing up to e-mail to get volunteers to test everything out, perform their normal operations, etc.
That's when I ran into an issue that is a show stopper in our case. We use CVS commit templates as an integration to our larger SCM system.
Basically we have a template:
Active Issues:
Where the Issues fields contain Scarab IDs and Description is more of the traditional commit message.
We have a precommit hook that makes sure the Issues: field have properly formatted IDs and that Description at least gets minimally filled in. I assume I can do this by modifying one of the hook scripts appropriately. (Subversion seems a lot more flexible than CVS on that front).
However, a little doc searching followed by bug database diving revealed that 1973 (Log message templates) wasn't yet implemented.
So, I am wondering what would be a good work around until 1973 trickles up to the TODO list?
Maybe setting the editor variable to a script? I'm not sure how it works in the svn case.
I'm trying to avoid:
* Developer does an SVN commit
or
* Developer does an SVN commit
While the idea of moving to SVN seems generally popular. I want to grease the wheels as much as possible and endure the minimum amount of grief from the "moved my cheese" crowd.
Any ideas for clever work-alikes?
Thanks much
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.