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

Re: svn diff output

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-09-16 03:51:48 CEST

On Wed, 2004-09-15 at 20:41, Eric S. Raymond wrote:
> Ben Reser <ben@reser.org>:
> > 1) Develop a new format that supports our features:
> >
> > Thoughts?
>
> I'm not a committer, so I'm not sure my opinion either counts or
> *should* count in a discussion like this.

You don't need to be a committer for this list to acknowledge a
well-thought out opinion. It's open to the public. :-)

>
> But for whatever it's worth, I support Ben's proposal. I even have
> a name for it: "action diff".

Subversion already has a function vtable called an 'editor_t'. It's the
main mechanism used to describe the difference between two trees: adds,
deletes, copies, propchanges, text-changes. (See svn_delta.h for a
verbose description.) That's how the svn client and server send
'action diffs' to each other right now... by marshalling these vtable
function-calls over a network.

We also already have a patch-like representation of these tree deltas:
it's our dump format. The dump format is meant to be portable, and has
an RFC-822 "look and feel". Take a look at it. It may be 90% of what
we need for defining this new patch format.

It's documented here:

  http://svn.collab.net/repos/svn/trunk/notes/fs_dumprestore.txt

The original versions 1 and 2 of this format always included full-texts
of files. But ghudson introduced format version 3 in svn 1.1, which
allows binary diffs instead of full-texts. That's a huge win.

Is this a good starting point? Doesn't it seem like we're mostly there?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 16 03:54:43 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.