Martin
I had the same question some time ago, I was using CVSNT/TortoiseCVS at
that time, and I received two very interesting answers from people at
CVSNT forum, which I quote here:
"Beat them over the head with a baseball bat each time they don't do it.
If you impose a technological 'solution', you'll just end up with a
whole load of comments of the form 'asdasdasd'. You need a social
solution, where *either* they see the benefit of comments *or* the pain
of not putting them in outweighs any time saved." [Crowther, Peter]
http://www.cvsnt.org/pipermail/cvsnt/2005-February/017488.html
"I sympathize with you, but there's no useful solution that you can
_impose_ on your users. They aren't "forgetting" to enter commit
comments. The dialog pops up everytime, so they have to deliberately
dismiss it. If they see no reason to write a comment, then they aren't
going to do it. If they are forced to write _something_, they'll write
garbage.
*You are going to have to change their attitude, not their software
settings.*" [Cornish, Merrill]
http://www.cvsnt.org/pipermail/cvsnt/2005-February/017491.html
In my opinion, both of them are right, you need to really convince your
developers to write something meaningful, a solution like the one
already proposed may be helpful but doesn't guarantee that the problem
will disappear.
Regards,
Juan Carlos
Martin Hantzschel escribió:
> Hello,
> Is there a way to obligue developers to write a message when commiting?
> People tend to forget, and i couldn't find an option to disable the commit
> button until a message has been written...
> Is that possibility available?
> Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Oct 4 23:40:30 2006