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

Re: Problems with the documentation of Subversion dump format

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 13 Dec 2011 09:52:27 +0000

esr_at_thyrsus.com (Eric S. Raymond) writes:

> # The "replace" action [?is only issued with directory copies, and?]
> # signifies that the existing contents of the directory should be
> # removed before the copy.

Replace applies to files as well.

> # Interpreting copyfrom_path for file copies is straightforward; the
> # target pathname gets the contents of the source pathname.
> #
> # Directory copies (the primitive beneath branching and tagging) are
> # tricky. For each source path under the source directory, a new path
> # is generated by removing the head segment of the pathname that is
> # the source directory. That new path under the target directory gets
> # the content of the source path.

Not sure what this means. This copies A/B/C to X/Y/Z:

Node-path: X/Y/Z
Node-kind: dir
Node-action: add
Node-copyfrom-rev: 10
Node-copyfrom-path: A/B/C

> # A single revision may include multiple copyfrom nodes, even multiple
> # copyfroms to the same directory, even mixed directory and file copies
> # to the same directory; [?Subversion client tools never generate such
> # mixed copies, but?] I have seen the results of cvs2svn doing it.

Not sure what "mixed directory and file copies to the same directory"
means or why Subversion clients would be restricted. Given directories
D1 and D2 and a file F it's trivial to copy D1 to D2/Dnew and F to

uberSVN: Apache Subversion Made Easy
Received on 2011-12-13 10:53:22 CET

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