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

Re: problem with dump/load

From: <cmpilato_at_collab.net>
Date: 2002-07-15 17:39:51 CEST

=?ISO-8859-1?Q?F=E9liciano?= Matias <feliciano.matias@free.fr> writes:

> > Why are you arguing with me? I helped to design the dump file format,
> > so I think I know a little bit about it.
>
> Sorry.

No sweat.

> > I think you're missing something crucial. While the dumper, as you
> > know, doesn't give content diffs (like Unified Diff or svndiff or
> > ...), it *does* give tree diffs. That it, every revision is described
> > as a diff against the previous revision. That's why only the changed
> > nodes show up in each revision, not the entire tree.
> >
> > When the dumper and loader where first written, they did exactly as
> > your patch did -- if either props or text changed, both were dumped.
>
> A new behavior (don't dump always both) that i missed.

Again, no sweat. Perhaps we just need to flesh out out documentation
a bit more.

>
> > The problem is that the following operations really are important for
> > us distinguish between:
> >
> > svn copy foo bar; svn ci
> >
>
> 'Node-path: bar
> 'Node-kind: file
> 'Node-action: add
> 'Node-copyfrom-rev: 4
> 'Node-copyfrom-path: /foo
> '
> '# no change. Go to next node or revision ...
> 'Node-path
>
> > svn copy foo bar; [edit bar's text]; svn ci
>
> 'Node-path: bar
> 'Node-kind: file
> 'Node-action: add
> 'Node-copyfrom-rev: 4
> 'Node-copyfrom-path: /foo
> 'Content-length-text: ??
> '...\n
> '# if change in props
> 'Content-length-props: ??
> '...\n
>
> we have a clean distintion between text/props and new content or no.
> For compatibility, the new loader need too always understand the old
> "Content-length".
>
> It's a proposition only.

Yeah, like I said in the other mail, its a proposition that I really
like, though we'd still want both the Content-length-* headers up with
the rest of the headers. So the absence of the Content-length-text
(-props) header would mean that the loader should avoid replacing that
node's text (props). If the header is present, it is treated as
explicit -- a value of 0 (9) literally means that that text (props)
should all be removed from the node.

Ben, Karl, Greg: do you remember why we didn't do this in the first
place? It really *is* a better solution, I think. Was it just so we
could have the conventional "Content-length" header?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 16 05:42:02 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.