Tree conflict merry-go-round on update/switch
From: Stephen Butler <sbutler_at_elego.de>
Date: Tue, 25 Nov 2008 17:55:14 +0100
Hi tree conflict fans,
I had another look at Mark Phippard's experiment with creating
Mark's original mail is here:
<http://svn.haxx.se/dev/archive-2008-10/1090.shtml>
If we skip the update of the victim, to be consistent with
I fixed some of the problems that Mark noticed, but not all.
An obvious solution is to record the tree conflict as resolved
An alternative design is to add a boolean "resolved" field to
A third alternative is simply to not include update/switch tree
Comments, anyone?
Steve
-- Stephen Butler | Software Developer elego Software Solutions GmbH Gustav-Meyer-Allee 25 | 13355 Berlin | Germany fon: +49 30 2345 8696 | mobile: +49 163 25 45 015 fax: +49 30 2345 8695 | http://www.elegosoft.com Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org For additional commands, e-mail: dev-help_at_subversion.tigris.orgReceived on 2008-11-25 17:55:33 CET |
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.