[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Error showing differences from log at branch creation

From: BIRD Neil <Neil.Bird_at_uk.thalesgroup.com>
Date: Fri, 25 Jan 2013 08:55:25 +0000

From: Ben Fritz [mailto:fritzophrenic_at_gmail.com], Sent: Thursday, January 24, 2013 9:35 PM
> On Thu, Jan 24, 2013 at 8:50 AM, BIRD Neil
> > If I create a branch *with changes* (e.g., copy modified working
> > copy to branch), then TortoiseSVN has problems showing the changes
> > that occurred as part of the copy.
> At least you have a workaround, I guess. What if you double-click
> the
> file in the first branch revision, when you do not have stop-on-
> copy
> selected? Obviously TortoiseSVN has the required data to do what
> you
> want, I'm perplexed why it wouldn't.

  This is when I don't have stop-on-copy selected.

> Why do you find it necessary to branch from a modified
> working copy? You could just as easily branch from the parent
> revision of the working copy, switch to the branch, and take your
> uncommitted changes along with your working copy to commit later.

  Well, yes, but it's a bit of a faff when SVN has a specific option to “branch working copy” (either via ‘svn cp . xxx’ or the option in TSVN's branch dialogue).

  And TBH, while not exactly tricky, it's not really “just as easy”!

Neil Bird    Principal Engineer    Tel: +44 (0)1293 587063
  Thales UK, Manor Royal, Crawley, West Sussex, UK, RH10 9PZ
  Work: neil.bird_at_uk.thalesgroup.com    Personal: neil_at_fnxweb.com
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-01-25 09:55:51 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.