Re: [Issue 422] Changed - "svn diff" needs to be fleshed out.

Greg Hudson wrote:

>>Oh, screw that. Big time. The server should never have to fork like
>>that. The only thing missing here is context within our
>>svndiff. Once we have that, then an svndiff can be transformed into
>>a context diff or a unified diff.
>>
>
>Oof. I don't think it's terribly easy to add context to a block-copy
>diff format. Maybe Branko has ideas on this. But I thought svndiff
>was only going to be used in cases where we expect to have the entire,
>unmodified diff source to work with.
>

Let me just make things plain here:

    * Only svndiff (and plain text) can go over the wire.
    * Svndiff does not (and can not, and does not need to) have context .
    * The server can generate svndiffs between arbitrary revisions.

>I think you're a little confused about the "custom diff program"
>feature people are talking about. This is for the output of the "svn
>diff" command, which generates user-readable data rather than svndiff
>data. You may still be right that no user is going to care, but it
>turns out to be a very easy feature to add (as long as we don't run
>the diff program on the servers).
>
Right. The server will never run any external diff programs.

-- 
Brane �ibej   <brane_at_xbc.nu>            http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org