> -----Message d'origine-----
> De : John Peacock [mailto:john.peacock_at_havurah-software.org]
> Envoyé : mardi 9 septembre 2008 15:59
> À : Roth, Pierre
> Cc : Matthieu BROUILLARD; users_at_subversion.tigris.org
> Objet : 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.
>
Sorry for my wrong answer. I did not really understand your use case.
Apologizes...
Pierre
---------------------------------------------------------------------
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 16:06:26 CEST