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

Re: svn commit: rev 5435 - in trunk/subversion: include libsvn_repos svnadmin

From: Florin Iucha <florin_at_iucha.net>
Date: 2003-03-23 17:17:24 CET

On Sat, Mar 22, 2003 at 07:22:29PM +0000, Philip Martin wrote:
> > (main): Add the --parent-dir to the option list for "load".
>
> I thought about making it "load-dir" rather than "parent-dir", but
> if/when there is a corresponding option to dump we may want to use the
> same name for both options. I also considered "root-dir" but in the
> end I decided to go with Florin Iucha's original.

The dump option might be harder to implement; look at this dump file
fragment:
   
   Revision-number: 3
   Prop-content-length: 113
   Content-length: 113

   K 7
   svn:log
   V 12
   Sample copy

   K 10
   svn:author
   V 6
   florin
   K 8
   svn:date
   V 27
   2003-03-23T16:06:26.451276Z
   PROPS-END

   Node-path: testdir/two
   Node-kind: dir
   Node-action: add
   Node-copyfrom-rev: 2
   Node-copyfrom-path: /one/two

The repository contents at revision 2 was

   .
   |-- one
   | |-- alpha
   | |-- beta
   | |-- gamma
   | `-- two
   | `-- alpha
   `-- testdir

What would the behavior of the dump --with-parent testdir be?
   * Dump only the contents under testdir.
      - Lose contents
      - Lose history
   * Refuse to dump.
      - What if one/ subtree was already exported and can be imported
        before the curent dump?
   * Dump only the contents under testdir and load only if revision 2
     has the Node-copyfrom-path at Node-copyfrom-rev.
      - What if they are different? Do we care?

florin

-- 
"NT is to UNIX what a doughnut is to a particle accelerator."

  • application/pgp-signature attachment: stored
Received on Sun Mar 23 17:18:04 2003

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.