Max Bowsher wrote:
> allan juul wrote:
>
>> hi
>>
>> on my system max os x [svn, version 1.0.9 (r11378)] the below command
>> doesn't work, which is surprising since the equivalent checkout command
>> does work
>>
>> this does *not* work
>> $ svn export http://svn.collab.net/repos/svn/trunk path/to/sub/dir
>>
>> this works
>> $ svn co http://svn.collab.net/repos/svn/trunk path/to/sub/dir
>>
>> this works too
>> $ svn export http://svn.collab.net/repos/svn/trunk path
>>
>> is that intended behavior ?
>
>
> max@zephyr [~/tmp] $ mkdir -p tmp/export/test
> max@zephyr [~/tmp] $ svn export $rs/trunk/notes tmp/export/test/here
> A tmp/export/test/here
> A tmp/export/test/here/repos_upgrade_HOWTO
> A tmp/export/test/here/repeated-merging
> A tmp/export/test/here/sql-backend
> A tmp/export/test/here/webdav-proxy
> ...
> A tmp/export/test/here/propfind-pool-notes
> A tmp/export/test/here/old
> A tmp/export/test/here/old/karlnotes
> A tmp/export/test/here/old/draft-korn-vcdiff-01.txt
> Exported revision 12610.
>
> Works for me.
well, you are pre-creating the directories [$ mkdir -p tmp/export/test]
i simply don't understand the difference in behavior between a checkout
and an export - they are totally identical apart from existence of the
.svn directory, right?. so what's the logic in the fact that the
checkout command *can* indeed create an arbitrary path but the export
command *can not* ?
./a
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 7 00:56:55 2005