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

Re: suggestion for 'svn import' behaviour

From: Pejvan BEIGUI <pejvan_at_online.fr>
Date: 2004-07-30 19:21:38 CEST

Campbell wrote:

> Pejvan BEIGUI <pejvan <at> online.fr> writes:
>
>>This seems to be the opposite behaviour of "Parent directories are
>>created in the repository as necessary.", which should automatically
>>create the "MacOSX_200-tome2" in the repository, right?
>>
>>thanks,
>>
>>Pejvan
>>
>
>
> That sentence about "parent directories" is questionably-worded. I think what
> it really means is that the destination URL you are specifying is going to
> be created in a similar way to "mkdir -p". Example: you import a new editor
> project into trunk/editors/myeditor, but your repository doesn't have
> trunk/editors/ yet at all, the parent of "myeditor/" will be automatically
> created.

Let's say that I also find this kind of example misleading:

> Once you have a tree of data ready to go, import the data into the
repository with the svn import command (see Section , “svn import”):
> $ svn import /tmp/project file:///path/to/repos -m "initial import"
> Adding /tmp/project/branches
> Adding /tmp/project/tags
> Adding /tmp/project/trunk
> Adding /tmp/project/trunk/foo.c
> Adding /tmp/project/trunk/bar.c
> Adding /tmp/project/trunk/Makefile
> ...

-- 
Pejvan BEIGUI                                     pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.

Received on Fri Jul 30 19:22:47 2004

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