Jean-Marc van Leerdam wrote:
> Hi Alex,
>
>
> On 27/03/07, AlexRayne <AlexrainPE196@hotbox.ru> wrote:
>> Hallow all!
>> i have try to apply an patch maked up by mercurial.
>> TSVNMerge wan`t to work with directories without SVN control.
>> than i try to apply the patch to a directory under svn,
>> but when Merge read one - it try to read some sources from repository
>> of cause unsuccessful, because this patch know nothing about svn
>> repository.
>> IMHO, merge tool should work with any patches that user want.
>
> No, TSVNMerge was created to present a GUI interface for handling
> patchfiles generated by Subversion for use within Subversion Working
> Copies. Nothing more, nothing less.
>
> Now, if a feature is easy to support outside a working copy, the
> developers may be willing to incorporate it. But only if they are
> asked politely and only if the feature is deemed useful.
>
> However, I don't think support for processing non-subversion patch
> files outside of Subversion Working Copies qualifies for inclusion.
The problem with 'other' patchfiles is that they're never properly
documented. When I started working on TortoiseMerge, I couldn't find any
good documentation on any diff format out there. The only one that was
at least partly documented was the Subversion unified diff format. And
even that I had to implement by trial-and-error until I got the parsing
algo right.
So my answer would be no, I won't implement other patch formats.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Mar 27 18:06:02 2007