You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Mark Eaton <me...@vasco.com> on 2003/11/17 06:08:15 UTC
svn import
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is it just me or does the svn import command not work as expected ?
I tend to do imports of new trees every so often and almost without faliure I
get it wrong every single time.
ie if I have a tree
proj
file1
file2
subdir1
....
I always end up doing a
svn import proj $SVNROOT/trunk/
which means I then have to go and move all the files around in the repository.
I would expect if I import a directory as above it would create the repository
path $SVNROOT/trunk/proj and all the subdirectories / files but rather it
imports everything under the proj directory but not the proj directory.
If I am the only one who thinks this works wrong then I'll just shut up =) but
it doesn't seem intuitive to me.
- --
Mark Eaton
Senior Software Engineer
VASCO The Authentication Company
+67 3511 5404
meaton@vasco.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/uGXPKd93Pkvz/M4RAs5PAJ4+3AoGWzfkBRggpFTZ8sCo9OoinACfUfpY
Np0M3NzQkauM63kq2TLlcT0=
=J4Ot
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn import
Posted by John Peacock <jp...@rowman.com>.
Mark Eaton wrote:
> I always end up doing a
> svn import proj $SVNROOT/trunk/
However
svn import proj $SVNROOT/trunk/proj
should work as you expected.
> If I am the only one who thinks this works wrong then I'll just shut up =) but
> it doesn't seem intuitive to me.
I have been bitten by this as well, but then I realized/remembered that import
(unlike other commands that affect the repository) will create as many
intervening directories in the target.
Most Unix tools (like cp and mv), when passed a directory as both the source and
destination, will create the source directory in the target for you (assuming
that was what you meant). However, 'svn import' acts more like this:
svn import proj/* $SVNROOT/trunk/
which is [mildly] suprising the first couple of times. You'll get over it. ;~)
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org