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

Re: Reintegrate merge and other SVN 1.5 issues

From: Stefan Kueng <tortoisesvn_at_gmail.com>
Date: Fri, 05 Dec 2008 18:50:04 +0100

golan davidovits wrote:
> Hi Stefan,
>
> Thanks a lot for your fast reply.
>
> First, I was happy to find out that sparse checkout is fully
> supported by Tortoise.
>
> I want to confirm with you my understandings from your reply (and
> previous threads you wrote):
>
>
> 1. If i work in branch reuse mode (repeating merges between trunk and
> branch) i should use the "Merge range of revisions" option and leave
> the revisions selection blank.

Yes.

> 2. About "mergeinfo" change in inner
> folders. I understand that It's something that can't be avoid in
> version 1.5. You have to commit or revert it. And it's going to be
> reduced in version 1.6. Is there any way (that i missed) that can
> help filter these modifications out from "check for modifications" or
> something else? Also, if some people commit the changes and other
> revert, isn't it going to cause a lot of conflicts in merges on these
> properties?

As mentioned, this should be improved in the upcoming 1.6 version.
In the meantime, you can check what exactly has changed from the commit
dialog by right-clicking on the column header and activating the
"property status" column. You can then see whether the file contents
have changed or only the properties of a file.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=980227
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2008-12-08 10:41:40 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.