If it is Windows, you can do with perl/Python.
Perl/Python can fetch the logmessage using "svnlook info -t TXN-NAME
 REPOS-PATH (the path to this repository)
 TXN-NAME (the name of the txn about to be committed)
are ordered arguments in pre-commit hooks (see pre-commit.tmpl).
Hope this will help you,
On Mon, Jun 16, 2008 at 10:13 PM, Robert Dailey <rcdailey_at_gmail.com> wrote:
> On Mon, Jun 16, 2008 at 11:35 AM, prakash tiwary
> <prakash.tiwary_at_gmail.com> wrote:
> > Hi Robert,
> > You can do it with pre-commit hooks at server side. The default
> > hooks does the same. All you need to do is follow the instructions inside
> > it.
> > Regards
> > Prakash
> > On Mon, Jun 16, 2008 at 9:32 PM, Robert Dailey <rcdailey_at_gmail.com>
> >> 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.
> I took a look at the server side pre-commit.tmpl, and it is using
> grep. I'm running this on a windows server, will this work? I'm not
> going to bother trying it until I can be sure. Thanks.
Received on 2008-06-16 18:54:11 CEST