[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: How to prevent empty log messages?

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: Mon, 16 Jun 2008 19:19:28 +0200

On Mon, Jun 16, 2008 at 6:02 PM, Robert Dailey <rcdailey_at_gmail.com> wrote:
> Hi,
> I'm sending this message to both the TortoiseSVN and SVN mailing lists
> because I'm not sure if this is a client side or server side issue.
> I want to setup the subversion server I have to not allow empty log
> messages. I read a few (very old) archived messages on the TortoiseSVN
> mailing list when TSVN was still around version 1. The old posts I
> read spoke of TortoiseSVN actually enforcing the "minimum length" for
> log messages. I've also heard of the server-side implementing a
> post-commit (maybe pre commit?) hook for this as well. I'm not sure
> which approach to take, assuming both options are open. I imagine this
> will probably have to be server-side, since I don't want to have
> everyone have to setup their client.
> If anyone could show me how to prevent empty log messages, I'd
> appreciate it. If this requires a post(pre)-commit hook, could someone
> post the code for that and tell me where to put it? Thanks.

If the limit is 60 characters, how are you going to make sure the log
message makes sense? How will you distinguish 60 characters of a
Shakespear verse, random characters or a meaningful commit message?

The reason we don't include a commit hook like that by default is
because we feel this is a social issue without a technical problem:
how long do you think it will take your users to find out they need to
specify 60 'x's?



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-16 19:21:15 CEST

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.