Quoting Simon Large <simon@skirridsystems.co.uk>:
> Jochem Schulenklopper wrote:
>> The case: for some fix --changes made in multiple files-- you want to
>> create a patch, but it should not contain all the files that are
>> locally modified. (There are other files in the directory with local
>> changes, but these don't belong to this fix.)
>>
>> An easy solution (w.r.t. end-user experience, not necessarily
>> development effort :-) for this would be to add a dialog in which the
>> user can select the files (s)he wants to be part of the patch. Just
>> like with committing or reverting, a list of locally modified files is
>> presented with all files selected per default. So, before the actual
>> patch is created, the user can deselect files that should not be taken
>> in consideration.
>
> This sounds like a good idea. I will add it to the issue tracker.
>
Wouldn't it be better if the fix is at least tagged as such separately in the
repository as well? And doesn't that give you the opportunity to create the
patch there, with only the relevant changes?
HTH
Jean-Marc.
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jul 26 11:21:25 2005