[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Property diffs as unidiff (Issue #1493)

From: Charles Acknin <charlesacknin_at_gmail.com>
Date: Mon, 10 Mar 2008 14:40:56 +0100

On Mon, Mar 10, 2008 at 1:05 PM, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> Look in the email archives for last year's Summer-Of-Code project on creating a
> Tree-Aware Diff/Patch Format that can represent any Subversion change including
> properties, and see if a format for property diffs was proposed there. If so,
> it might be a good choice, or if no conclusion was reached the discussion might
> provide some hints.

Well I can tell right away that the work that's been done wrt the new
patch format during last year's GSoC is not what Daniel is looking
for. Indeed, the new patch format was designed to serialize any
change of a tree and make it *transportable* between working copies
(as opposed to visually readable for code review) for later patch

[what it does is that while traversing (i.e. during 'svn diff') the
working copy for changes (a) text-changes are left as unidiff and (b)
other non-unidiff-able changes such as {property, binary and tree}
changes are serialized into basically ra_svn protocol bytes before it
all get dumped to the output along with the unidiff. This way, 'svn
patch' can tell apart from the unidiff and the svnpatch bytes and
dispatch the tasks accordingly in order to apply the patch (the
unidiff with text-changes is forwarded to patch(1) and the svnpatch
chunk is processed internally).]


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-10 14:41:14 CET

This is an archived mail posted to the Subversion Dev mailing list.