--- Ben Collins-Sussman <sussman@collab.net> wrote:
> A post-commit hook that performs another commit?
>
> You'd better be careful about infinite loops.
I hear ya ;-)
> The only way to do that, I think, is write a
> post-commit script that
> uses libsvn_fs directly, either in C or python:
>
> 1. look at the new revision, see if custom
> property is attached.
> If it is, do nothing.
>
> 2. create a txn. call fs_copy() to make your
> tag. call
> fs_set_txn_prop to create a custom property.
> call fs_commit().
I'll keep this in mind.
OTOH, I think it'd be much simpler if the trigger can
know what's being acted on. For example:
1. If the trigger were executed from the creation of a
per-branch revision label, don't do anything
2. If the trigger were executed from the creation of a
branch and this branch is not LATEST, create the
LATEST branch and the 0 label.
3. Otherwise, create the per-branch revision label and
increment the revision counter attribute on the
branch.
Oh, another question:
3. Does the post-commit trigger execute for each
element in the commit, or once per commit command?
Thanks,
Noel
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 21:52:24 2002