Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 28B1FDAA9 for ; Tue, 9 Oct 2012 15:24:01 +0000 (UTC) Received: (qmail 23728 invoked by uid 500); 9 Oct 2012 15:24:00 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 23651 invoked by uid 500); 9 Oct 2012 15:23:59 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 23639 invoked by uid 99); 9 Oct 2012 15:23:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 15:23:59 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tinu44@gmail.com designates 209.85.214.171 as permitted sender) Received: from [209.85.214.171] (HELO mail-ob0-f171.google.com) (209.85.214.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 15:23:51 +0000 Received: by mail-ob0-f171.google.com with SMTP id 16so7054817obc.16 for ; Tue, 09 Oct 2012 08:23:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=oDyYrRJuHVlUNdSyf+QYSf1wQyEJ7eWmu/zdKKa5IyM=; b=nKucfI74zOf/GmUH81He1mmnRO+/00JqnSuqC2tLEavoy8XzhPTRmTFOz+Yxd9S4et dq2nE7wbDdLfYltla0pt7HRGsFWmAHCAIjCq0RCka00D1sZAwKyQIzgmSkQqO6gnLc86 JGf/7EHCVmynhYYw+FAnFx7YauMr2Xel3jHhMQbaKQBja1tCp2hJtGzPACOfVbyKk1cj It95g2yH7OmB1TkaRcoLcDncJoQ4/GHQSmUHgGMjGtsktnyv7h8aU8Zc1x+DyrEc2Aq/ GURhXOUu2BfyjhaFZeYxw9MiDonjHb5qZ+YMdoEFnd9CZMSV1284C2GNweFxbTpk9uY2 XC9g== MIME-Version: 1.0 Received: by 10.60.32.241 with SMTP id m17mr3239878oei.50.1349796210495; Tue, 09 Oct 2012 08:23:30 -0700 (PDT) Received: by 10.76.9.232 with HTTP; Tue, 9 Oct 2012 08:23:30 -0700 (PDT) Date: Tue, 9 Oct 2012 17:23:30 +0200 Message-ID: Subject: How to merge a rename of a folder From: Martin Bischoff To: users@subversion.apache.org Content-Type: multipart/alternative; boundary=e89a8fb1ebd4a5507f04cba1ebcd --e89a8fb1ebd4a5507f04cba1ebcd Content-Type: text/plain; charset=ISO-8859-1 I have a project which is being developed on /trunk, and at the same time I have a branch (/branches/1.x) for maintenance of version 1.x. Now I'd like to rename a folder of the project, e.g. /trunk/a to /trunk/b. The same folder should also be renamed on the maintenance branch, so that future bugfixes (made inside /trunk/b) can be merged to the branch. If I merge the revision (in which /trunk/a was renamed to /trunk/b) to the branch, then it seems that files inside /branches/1.x/b will then be identical copies of the files inside /trunk/b at the HEAD revision. This means, that for example, any changes made directly on /branches/a/text.txt are then lost. Obviously I'm doing something wrong! What is the correct procedure to merge a rename of a folder to a branch? Should I rename the folder independently on both trunk and the branch? Will I then still be able to merge changes from /trunk/b to /branches/1.x/b? BTW: I'm using the current version of TortoiseSVN, so I can't give the exact svn commands that were used. Thanks a lot for any help. -Martin --e89a8fb1ebd4a5507f04cba1ebcd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have a project which is being developed on /trunk, and at the same time I= have a branch (/branches/1.x) for maintenance of version 1.x.

Now I= 'd like to rename a folder of the project, e.g. /trunk/a to /trunk/b. T= he same folder should also be renamed on the maintenance branch, so that fu= ture bugfixes (made inside /trunk/b) can be merged to the branch.

If I merge the revision (in which /trunk/a was renamed to /trunk/b) to = the branch, then it seems that files inside /branches/1.x/b will then be id= entical copies of the files inside /trunk/b at the HEAD revision. This mean= s, that for example, any changes made directly on /branches/a/text.txt are = then lost.

Obviously I'm doing something wrong!

What is the correct pro= cedure to merge a rename of a folder to a branch?

Should I rename th= e folder independently on both trunk and the branch? Will I then still be a= ble to merge changes from /trunk/b to /branches/1.x/b?

BTW: I'm using the current version of TortoiseSVN, so I can't g= ive the exact svn commands that were used.

Thanks a lot for any help= .

-Martin
--e89a8fb1ebd4a5507f04cba1ebcd--