Am Freitag, 8. Juni 2018 17:08:06 UTC+2 schrieb Stefan:
>
>  
>> Okay, I understand. But isn't there a differnt (or better) way to do 
>> that? I mean, it's still possible to "export" the file or "save revision 
>> to" (isn't that the same actually?), so you can get a copy of the file at 
>> the specified revision and compare it to a file from the disk. Should be 
>> quite straightforward...?
>>
>> For one file, yes.
> if you show the log for a folder, there can be thousands of changed files 
> per revision. Do you really want then to fetch each of these files 
> separately and start an instance of the diff viewer for each of those?
> I really doubt that...
>
> And no: doing that for e.g. 5 files and fall back to the patch-file for 
> more won't work either: you can be sure that no matter what setting we use 
> it won't suit all users.
> And having an option to configure that won't help either: imagine you've 
> configured the value to 20 because you're working on a repo on a local 
> server so it's fast. Then you do the same on a remote repo - and again 
> users will complain.
>
> Stefan
>

Okay, accept that.
The only remaining way I can think of may be: Why not ignore such a file in 
this situation?
I have to admit that this file may contain any content, so it cannot be 
ignored easily. The solution could be adding exactly that option which I 
used the file for: add the option "do not merge automatically", or "always 
prompt for user confirmation on merge". And then, this option could be 
ignored during merging for file comparison.

What about that?

-- 
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/8c7c003d-2968-4942-826c-857f7e9b90db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to