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

Re: Bug: can't create patch in git format

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Sat, 23 Feb 2013 11:19:00 +0000

On 18 February 2013 20:23, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 17.02.2013 16:56, Flávio Etrusco wrote:
>> Hello,
>>
>> Using TortoiseSVN 1.7.11, Build 23600 - 32 Bit on Windows 7 32-bit,
>> triggers an error message: "<temp_folder> is not a working copy"
>> (where <temp_folder> is the path in %TEMP%).
>
> Works fine for me.
> I suspect you have some shell extension installed that changes the CWD
> (current working directory) of a process when the file-open dialog is shown.

I can also reproduce this using an older nightly build on Win7. But
the error message is not exactly as reported here for me.

In a working copy with one file changed, create patch for fred.txt or
for fred.txt parent folder.
Select git format
On save the error message dialog shows:
---------------------------
TortoiseSVN
---------------------------
'C:\Users\Simon\AppData\Local\Temp\fred.txt' is not a working copy
---------------------------
OK
---------------------------

If the folder contains several modified files create patch stops with
a similar error message on one of the modified files. Sometimes one
file will get processed correctly, but I can't see much pattern to it.
The error is only with git patches, not svn patches.

Simon

-- 
:       ___
:  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=3049639
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-02-23 12:19:09 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.