This is interesting. I just tried it out (besides, I'm using 1.1.0rc3 on Windows here, but I saw the effect with 1.0.x on Linux, too)
The two versions should give the same result, but only the second version behaves like I would expect svn to behave.
-----------------------------------
~> svn import testprj <repos>
Adding testprj/test1.c
Adding testprj/test2.c
~> svn list <repos>
test1.c
test2.c
----------------------------------
~/testprj> svn import . <repos>
Adding testprj/test1.c
Adding testprj/test2.c
~> svn list <repos>
testprj/
~> svn list <repos>/testprj
test1.c
test2.c
----------------------------------
Thanks, François, for the workaround. It works fine for me. But I think the two versions abouve schould bring the same result.
Regards Martin
-----Original Message-----
From: François Beausoleil [mailto:fbeausoleil@ftml.net]
Sent: Dienstag, 21. September 2004 14:25
To: Runge Martin (SMS SEC SW Augsburg External)
Cc: dev@subversion.tigris.org
Subject: Re: Confusing behaviour with import
Runge.External2@infineon.com wrote:
> Hi *,
>
> I just came to the following issue:
>
> Imagine a small project called 'testprj' with two files, 'test1.c' and
> 'test2.c', that reside inside the folder testprj/
>
> testprj/
> |- test1.c
> |- test2.c
>
> when doing an 'svn import testprj/ <repos>', the files test1.c and
> test2.c get imported directly into <repos> without creating the folder
> testprj in <repos>. This behaviour can be seen in the various GUI tools,
> too. You mark 'testprj', say import to <repos>, and testprj/ is not
> imported, only the two files.
If you do svn import . <repos>, what would you expect ? The command I
wrote is the exact same command as yours, except mine needs to be in the
right folder for that to work.
Hope that helps,
François
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 21 16:04:32 2004