On Oct 11, 2009, at 11:21, Pat Farrell wrote:
> Mark Eichin wrote:
>> You can't not have a log - you can merely have a blank one.
>> (Repositories are cheap, try it :-) While it's probably fine for
>> your
>> use, it's a bad habit - one of the more common commit hooks is one
>> that
>> rejects the commit if the log is blank...
>
> I really dislike that commit hook, as tends to have folks enter
> "comment" just to not be blank.
A pre-commit hook to check the length of the commit message should
only be there to serve to remind the developer of something he should
already want to do but has momentarily forgotten. It is assumed you
already have a policy that states that developers should describe
their commits. If you have developers who are deliberately subverting
your checks and disregarding your log policy, then you have a social
problem with your developers, and not a technical problem with your
repository.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2406503
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-12 04:12:43 CEST