Re: start-commit log message.

2015-03-31 Thread Carlos Alberto Costa Beppler
Only to record. I solved the problem looking for ephemeral properties on commit. They are only sent for 1.8 clients. To do this I changed my start-commit hook was to this: #!/usr/bin/env python # The start-commit hook is invoked before a Subversion txn is created # in the process of doing a com

Re: start-commit log message.

2015-03-31 Thread Carlos Alberto Costa Beppler
Sorry for asking without proprer documentation read and thanks. There is a way to "detect" that the log message is not sent because of an older client version? My intent is to block the commit early if I can. On Tuesday, March 31, 2015 at 12:28:37 PM UTC-3, Andreas Stieger wrote: > > Hello, >

Aw: start-commit log message.

2015-03-31 Thread Andreas Stieger
Hello,   > validate the log message [...] start-commit [...] > [...] > if the client is using an older version (like 1.7) the commit message > obtained > using svnlook is always empty durng the start-commit. In this case the commit > message is available only during pre-commit.   Yes, and this

start-commit log message.

2015-03-31 Thread Carlos Alberto Costa Beppler
Hi, I'm trying to validate the log message using the new 1.8 start-commit capability of inspect the transaction beeing created. My problem is that if the client is using an older version (like 1.7) the commit message obtained using svnlook is always empty durng the start-commit. In this case th