Brock Janiczak <firstname.lastname@example.org> wrote on 03/09/2005 05:14:53
> I was suggesting the second one (quick fixes that run either revert,
> or edit conflicts), but I forgot that SVN automatically merged the
files for you :)
> So, the first first option you suggested would be the way to go. It
> good to have a resolve action too if the user has manually fixed the
> (they can alwyas use the team context menu too).
> If you want, i could knock them up on the weekend.
> This could be hooked up in ConflictsCompareEditorInput. The problem is
> the editor may have to be closed (or closing) when the resolve happens.
> will need to try this out...
Ideal would probably be if it asked you when you close the editor if you
want to resolve the conflict.
> We do pick up changes to the .svn files though a resource listener
> the folders to be refreshed) so it should be possible to catch the new
> conflicted statuses with the notify listener. It might even be possible
> hook it into the Sync info...
> If i get a chance, i will look at alternatives, but your scheme does
> I am not too worried.
I agree that a listener could probably do it as well.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Thu Mar 10 03:34:12 2005