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

Re: Patch file creation: Anchoring inconsistent

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 3 Aug 2016 20:32:23 +0200

On 03.08.2016 18:04, Daniel Hoenig wrote:
> There are two ways to create a patch file:
> 1- in Windows Explorer right click on a folder, Tortoise context menu "Create patch"
> 2- in the Tortoise mdofociations window, right click on a selection of files, context menu "Create patch"
>
> However, the two patch files created differ.
>
> Example:
>
> Top-level folder MyProject which is used as base for both scenarios 1 and 2.
> A file MyProject/1/2/code.c
>
>
> In scenario 1, the patchfile contains the full path (good)
>
>
> Index: 1/2/code.c
> ===================================================================
> --- 1/2/code.c (revision 66174)
> +++ 1/2/code.c (working copy)
>
> whereas in scenario 2 it contains only the filenames (bad)
>
> Index: code.c
> ===================================================================
> --- code.c (revision 12345)
> +++ code.c (working copy)
>
>
> The full path is important for anchoring in the code review tool Crucible.
>
> The Tortoise modification window, although started from the parent folder, shows inconsistent behavior by using no path.

That's actually by design: users requested a long time ago that a patch
from the CfM dialog should use the filenames only as the path.

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=3181108
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-08-03 20:32:40 CEST

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