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

Re: svn commit: r1375675 - in /subversion/trunk/subversion: include/svn_repos.h libsvn_repos/fs-wrap.c libsvn_repos/hooks.c libsvn_repos/repos.c libsvn_repos/repos.h tests/cmdline/commit_tests.py tests/cmdline/svntest/actions.py

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 21 Aug 2012 15:37:11 -0400

On Tue, Aug 21, 2012 at 3:29 PM, C. Michael Pilato <cmpilato_at_collab.net> wrote:

> If the community decides to simply modify start-commit to run *after* the
> txn gets created and populated with txnprops, that's fine with me. I
> assumed that that change was undesirable due to the fact mentioned
> elsethread about how start-commit would no longer be useful for keeping a
> would-be read-only repository read-only.

start-commit does not currently receive the txn-id, so I do not see
how we can use/move it for svn:log access anyway. How about a single
new hook called something like start-commit-txn or something like
that?

FWIW, I agree it would be nice to have access to svn:log before the
data is sent from the client. People could do a lot with that, and if
it is easier to attach the client version to the txn properties, then
that is another good reason.

IMO, we have had a LOT of users@ requests for the client version in
hook scripts.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2012-08-21 21:37:43 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.