On 25.02.2013 15:32, Jeff Hedlund wrote:
>> On 22.02.2013 17:48, Jeff Hedlund wrote:
>>>> On 22.02.2013 15:37, Jeff Hedlund wrote:
>>>>> I still want to use TortoiseSVN as part of the process, to be
>>>>> able to choose which files to patch for example, but I don't need
>>>>> to see the file "save as" dialog - I can automate the name of the
>>>>> file and save to a temporary directory, automatically upload to
>>>>> our issue tracker with proper flags, etc.
>>>>>
>>>>> So I am looking for an /outfile parameter to the
>>>>> /command:createpatch that would auto-save the resulting patch
>>>>> file.
>>>>
>>>> svn diff path/to/file path/to/file2 > patchfile.txt
>>>
>>> Yes, but that doesn't give the TortoiseSVN UI of selecting the files
>>> to include in the patch (see previous post).
>>>
>>> In our workflow, we create the patch using TortoiseSVN Create Patch
>>> then selecting the appropriate files via checkboxes and also many
>>> times take the opportunity to review the changes in the TortoiseSVN
>>> UI before creating the patch.
>>
>> pass /savepath:"path/to/file/to/save" on the command line to skip the
>> save-as dialog.
>
> That is great, just what I was looking for, thanks!
>
> Does there happen to be a command line option to not open the patch after creating it?
No, but I'll add one.
--
___
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=3049773
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-02-25 19:59:49 CET