Markus Schaber wrote on Wed, Jul 27, 2011 at 09:37:38 +0200:
> Hi, Andreas,
> Von: Andreas Krey [mailto:a.krey_at_gmx.de]
> > On Tue, 26 Jul 2011 13:55:17 +0000, Les Mikesell wrote:
> > ...
> > > How could it possibly be up to date if there has been a commit since
> > > the last time it was updated?
> > Because the commit came from my WC. My WC was up to date before the
> > commit, and the only things that change have been in my WC already, so
> > there is no possible way my WC can not be up to date.
> That assumption is wrong, I guess. As far as I know, commit hooks can
> modify the commit. (This behavior is discouraged, but nevertheless it is
Modifying the txn handed to the hook is discouraged because it's not
possible to communicate the changes to the client, so its working copy
becomes inconsistent with the repository.
It's trickier but possible to write a hook that inspects the provided
txn, /recreates/ it (possibly with modifications), commits /that/, and
then rejects the originally-provided txn. The client working copy is
consistent and will remain consistent after an 'svn up' (which will
merge cleanly or conflict, as usual).
> Best regards
> Markus Schaber
> We software Automation.
> 3S-Smart Software Solutions GmbH
> Markus Schaber | Developer
> Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 |
> Fax +49-831-54031-50
> Email: email@example.com | Web: http://www.3s-software.com
> CoDeSys internet forum: http://forum.3s-software.com
> Download CoDeSys sample projects:
> Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner |
> Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
Received on 2011-07-27 21:37:10 CEST