RE: How do I prevent auto-merge?
From: Karan, Cem \(Civ, ARL/CISD\) <CKaran_at_arl.army.mil>
Date: 2005-04-08 15:47:23 CEST
I see what you're saying, I just don't want things to break because of an automerge allowing two mutually incompatible changes to end up in the same file at the same time. Theoretically, regression tests should catch that almost immediately (and LONG before the next commit), but that isn't guaranteed. My hope is that if all files that are different can be marked as being in conflict, then I can use the same procedures for resolving potential conflicts as I use for real conflicts.
The big use of this would be for the future; one thing that it would be possible to do is to write a GUI tool that understands subversion's conflict presentation format (both the fact that there are several files & the format within the files) to help the user resolve the conflicts. Files that would have been automerged will show up in the system in exactly the same way as real conflicts, which would reduce the amount of effort necessary to figure things out (only one way, rather than two).
Thanks,
-----Original Message-----
Johan Appelgren wrote:
Why not just allow the merge to work normally since the merge will
This scheme works great for my uses. Is there some other reason that
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.