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

dump format refinement

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-04-29 22:09:15 CEST

A lot of private discussion seems to indicate that everyone really
prefers the second dump format much more than the first. Here's a
refinement of that format, done by example.

Refinement of proposal #2: (after discussion with gstein)

Start with all RFC822-style headers at the top. The final header will
be a 'Content-length:', followed by the content. Thus our record
boundaries can be inferred.

The content section will have two implicit parts: a property hash, and
the fulltext. The division between these two sections will be implied
by the "END" tag at the end of the prophash. In the case of a
directory node or a revision, only the prophash will be present in the

Here's an example of revision 1422, whereby I added a new directory
"baz", added a new file "bop" inside it, and modified the file "foo.c":


Revision-number: 1422
Content-length: 74

K 6
V 7
K 3
V 17
Added two files, changed a third.

Node-path: /bar/baz
Node-revision: 1422
Node-kind: dir
Node-action: added
Content-checksum: oj3eu729
Content-length: 29

K 10
V 4

Node-path: /bar/baz/bop
Node-revision: 1422
Node-kind: file
Node-action: added
Content-checksum: bzz35te7
Content-length: 124

K 12
V 15
K 14
V 2
Here is the text of the newly added 'bop' file.

Node-path: /bar/foo.c
Node-revision: 1422
Node-kind: file
Node-action: added
Content-checksum: Ae73te7et
Content-length: 105

Here is the fulltext of my change to an existing /bar/foo.c.
Notice that this file has no properties.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 29 22:12:45 2002

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.