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

Re: start-commit log message.

From: Carlos Alberto Costa Beppler <beppler_at_gmail.com>
Date: Tue, 31 Mar 2015 08:34:07 -0700 (PDT)

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,
> > 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 is expected, documented [1] and will not change. Quoting:
> [[[
> Note: Subversion does not require that commit transaction properties (such
> as the revision log message) be attached to the transaction as part of its
> initialization. As such, some clients will still not provide that
> information to the server until after the start-commit hook has been
> invoked. Here is a list of such clients we are aware of:
> Pre-1.8 clients communicating via HTTP
> Clients communicating via HTTP when mod_dav_svn's
> "SVNAdvertiseV2Protocol" option has been set to "off"
> Administrators should consider modularizing the tests that their hooks
> perform on transaction properties, invoke those tests from both the
> start-commit and pre-commit hook scripts."
> ]]]
> You will need to run the same hook again as pre-commit.
> [1]
> https://subversion.apache.org/docs/release-notes/1.8.html#hooks-start-commit
> <https://www.google.com/url?q=https%3A%2F%2Fsubversion.apache.org%2Fdocs%2Frelease-notes%2F1.8.html%23hooks-start-commit&sa=D&sntz=1&usg=AFQjCNG5AarLHZr4kAfA6cuRwPNj6Qeohg>
> Andreas
Received on 2015-03-31 17:34:38 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.