Paul Libbrecht <paul@activemath.org> writes:
> We recently played with the cmd-diff and cmd-diff3 settings in the
> hope of getting "pluggeable diffs" as we wished... and... well.. it
> works but it is not at all what we understood as pluggeable diffs.
>
> Namely, we had expected such a setting to be the diff used to compute,
> at commit time, the difference to be stored in the database (more or
> less equivalent to what's stored as fragements of the ",v" files of
> CVS), and, at update time, the merge algorithm to modify the files.
Er, no, that's not at all what it is. Subversion uses a binary
differencing algorithm, very *not* pluggable, for getting information
to and from the repository. The --diff-cmd and --diff3-cmd options
are just for setting the programs used to generate contextual diffs,
client-side only, for the purposes of display and merging.
> We have an XML-diff and would like to put it to use inside such a tool
> as subversion. The latter should provide us the storage and transport
> mechanism, being agnostic of the data of the diffs and
> updates... Maybe I should call this the "patch" format.
Subversion is already agnostic -- it treats all files as binary when
transferring changes between repos and client.
> Did I understand wrongly ? How hard would it be to modify
> Subversion so that the patch-format is pluggeable.
Why would you actually want this? I think some real use-cases --
including where Subversion is failing you now -- would help out here.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 26 16:33:59 2004