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

Re: svn commit: r1029751 - in /subversion/trunk/subversion: include/svn_client.h libsvn_client/export.c svn/export-cmd.c tests/cmdline/export_tests.py

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Mon, 01 Nov 2010 18:35:30 +0000

Julian Foad <julian.foad_at_wandisco.com> writes:

>> - * @a to is the path to the directory where you wish to create the exported
>> - * tree.
>> + * When exporting a directory @a to is the path to the directory where
>> + * you wish to create the exported tree, when exporting a file it is
>> + * the path of the file that will be created. If @a to is the empty
>> + * path the name of the file/directory in the repository will be used.
> I'm not sure that last sentence is true for a directory, only for a
> file.

It describes the command line client behaviour, and the client doesn't
distinguish files/directories when calling svn_client_export5.

> I think this doc string may need to explain more subtleties to the total
> behaviour, but I haven't quite grokked it all. For example: does it
> make any difference whether the specified path already exists on disk?
> For a dir, is the exported tree's root created *at* or *below* the
> specified dir?

There is a difference between files and directories, files overwrite
while directories give an error saying "use --force".

Received on 2010-11-01 19:36:26 CET

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.