Re: Automatic replacement on commit

Roth, Pierre wrote:
>> * using a post commit-hook that will fire a process that
>> will automatically update the file and then commit it again?
>
> You'll probably have to use a pre-commit hook instead of a post-commit
> one. Just before committing, your script will change the file header and
> on success, the file (or list of files) will be commited.

No, that isn't a supported model. If you change the file in pre-commit,
then the working copy that made that commit contains the wrong data
(i.e. what it sent is not what was committed) and there is no way to
resolve that error.

The choice is either:

1) validate the data in a pre-commit hook and refuse the commit if it
doesn't checkout fine;

2) do as the OP suggested and update the file in post-commit and commit
that as an independent change.

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-09 15:59:09 CEST