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

Re: feature request: commit warning for switched subtrees

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: Wed, 21 Oct 2009 07:33:01 +0200

Hi Todd,

2009/10/21 Todd C. Gleason <tgleason_at_impac.com>:
> I just tried this using TSVN 1.6.5, and it was as I said:  TortoiseSVN offered to commit all the files from both locations.
> In more detail:
> 1.  I edited within folder 1 in my branch WC
> 2.  I edited within folder 2 in my trunk WC
> 3.  I copied folder 1 from my branch WC into my trunk WC, overwriting the contents of the trunk WC's folder 1 (including .svn dirs).
> 4.  I selected Svn Commit...
> 5.  Both the files in folder 1 (copied from the branch) and folder 2 (always the trunk) displayed in the commit dialog.
> 6.  I verified that the Svn path of the copied folder 1 is still the branch, while folder 2 is the trunk, as is the parent of folders 1 and 2.

Sure, this is expected. A nested layout with parts coming from one and
the same repository can be committed in one go. That's intended and
frequently preferred behavior (even if it's not always expected by the

I can see why in some situations it would be beneficial to inform
users about the fact that the commit about to take place spans one or
more nested folders. That information is available to the user if
he/she carefully examines the 'path' column, but given any reasonably
sized WC and/or repository the different paths may be hard to catch at
a glance.

.       ___
.  @@  // \\      "De Chelonian Mobile"
. (_,\/ \_/ \     TortoiseSVN
.   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
.   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-21 07:33:11 CEST

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