I don't have any problem creating a patch via TortoiseSVN / Create patch... 
on the root - it includes relative paths as expected. [image: tortoisesvn 
patch.png]

On Thursday, 28 July 2022 at 20:13:39 UTC+10 Ivan Zuboff wrote:

> Console command "svn diff" from the root of the repo shows patch/diff with 
> long relative paths, contrary to TortoiseSVN from the root while creating 
> patch or showing unified diff.
>
> четверг, 28 июля 2022 г. в 13:05:25 UTC+3, Ivan Zuboff: 
>
>> Hello!
>>
>> Say I'm having a repo with the following structure: /a/1, where a is 
>> folder and 1 is file in this folder. If I edit file "1" and create a patch 
>> from the top of my repo, it will contain no relative path mentioning "a" 
>> folder":
>> Index: 1
>> ===================================================================
>> --- 1    (revision 123)
>> +++ 1    (working copy)
>> // changes here
>>
>> This causes guessing when applying the patch. Obviously guessing is not 
>> always working right in non-trivial repository. When I edit Makefile in 
>> some subfolder and do nothing else, my patch doesn't contain any clue about 
>> what Makefile exactly should be patched. Sadly, this is a long-standing 
>> problem for me and my collegues with TortoiseSVN.
>>
>> If repo would also contain file /2 and I would edit it too, then patch 
>> would look different (like I would like to see it): I would get "a/1" 
>> instead of just "1" and guessing would work much better on applying. 
>>
>> Can I always create a patch with relative paths ("a/1" instead of "1") 
>> via TortoiseSVN? Is there any option that enables this behavior?
>>
>> Thank you very much in advance.
>>
>> Best regards, Ivan
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/f0864ce5-c0a9-48fa-afa2-a351d02929fbn%40googlegroups.com.

Reply via email to