I bought and use Versions, and use Subcommander for svn merge + svn
switch. I guess I'll add my +1 on the chance it might help to
influence the developers, and add what I posted a year ago, expanding
on Ray's suggestion to share how we use our tools..

Our workflow uses developer branches, that we merge from a dev branch.
We then switch our working copy to the dev branch, merge remote dev
with second source of our branch (now remote), then merge that back to
remote dev branch, then switch our wc back to our branch.

In Subcommander, merge is from a contextual menu of a revision (or
span of revisions) from a log. switch is from a contextual menu from a
browse repository view.

On Jun 1, 7:30 am, Ray <raimondi...@gmail.com> wrote:
> I've never used a tool other than command line svn and a text editor to
> handle merges because all of my merging has been pretty simple.  However, I
> would probably become more adventurous with what I used merging for if I had
> a good tool to help me with it.
> To make this thread more helpful to the Versions team, would people be
> willing to outline what they like or don't like about the merge tools they
> currently use?  Then Versions may become even more of an obvious choice.
>
> -Ray
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Versions" group.
To post to this group, send email to versions@googlegroups.com
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to