Re: How to Modify the transaction file

> > And one more question is will this operation cause the inconsistence
> > between the WC and REOPS?

> That's exactly why you mustn't modify a transaction: the working copy
> will think it has a file at, say, revision 42, but the repository
> will think revision 42 looks different. When you later try to update,
> things will blow up.

Technically I suppose it would be possible to change the transaction
handshaking such that rather than updating the Working Copy to the
committed revision it is reverted to the pre-commit revision if the
transaction is server-side modified - and notifying the user of the
need to pull the commit from the server. This might make it possible
to perform such actions - it sounds like an ugly workflow to me
(though of course only applies when servers change a transaction).

Best to just make it a pre-commit condition with feedback and get the
user to apply the changes locally and recommit.

I'm not sure you want to be inserting that text every time though...
Doing this on trunk and branch would ensure merge conflicts as both
would have differing changes in the file at the same position.

--
Aaron
> >       I think the Subversion svn:keywords auto substitution may work of
> > the same mechanism? Any one tell me how to do this?
>
> Keyword substitution works differently. It works on the client side
> only. The keywords are only expanded to their actual values upon
> checkout or export; they're not stored that way in the repository.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org