On Oct 17, 2005, at 02:30, Daniel Berlin wrote:
> export, unfortunately, behaves differently than checkout. If you do
>
> svn export svn://gcc.gnu.org/svn/trunk/gcc/doc/install.texi gcc
>
> It creates a file named "gcc" in the current directory, containing the
> contents of install.texi
>
> Fair enough, though different than checkout, which if you could
> checkout
> a single file, presumably would have put it in gcc
>
> So i create a dir named gcc
>
> -bash-3.00$ mkdir gcc
> -bash-3.00$ svn export file:///svn/gcc/trunk/gcc/doc/install.texi gcc
> svn: Can't move 'gcc.2.tmp' to 'gcc': Is a directory
>
> I *know* it's a directory.
> That's why i gave it to you. To put the file in.
>
> IMHO, export's extra argument should behave exactly like the one to
> checkout, and effectively copy the file into that path.
>
> The current behavior is just not sensible.
>
> We had a discussion about whether to create the empty paths that
> are in
> the URL or not (like CVS), and the consensus seemed to be no
>
> But nobody disagreed that what happens now doesn't match the checkout
> behavior, and probably should.
The workaround would seem to be:
$ mkdir gcc
$ svn export file:///svn/gcc/trunk/gcc/doc/install.texi gcc/install.texi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 17 12:24:56 2005