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

Re: Export behaving badly

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2005-10-17 15:55:22 CEST

On Mon, 2005-10-17 at 15:46 +0200, Branko ╚ibej wrote:
> Daniel Berlin wrote:
>
> >So i'm converting over some documentation update scripts from gcc.
> >
> >They do the following:
> >
> >Export a bunch of doc files from repo
> >build docs
> >place them somewhere
> >
> >export, unfortunately, behaves differently than checkout. If you do
> >
> >svn export svn://gcc.gnu.org/svn/trunk/gcc/doc/install.texi gcc
> >
> >
> I think export should simply fail for a single file, just like checkout.

Checkout fails because it can't currently maintain a working copy
alongside the single file

Export doesn't fail because it doesn't need such a working copy.

Why put restrictions on export that doesn't need to be there?
We actually want to remove this checkout restriction, not propagate it
to other things.

> We have "svn cat" for that.

By this argument, svn export is completely useless. You could make the
directory structure on your own and cat into it one file at a time.

Should we remove export because we have "cat for that", and instead tell
people to script the equivalent?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 17 16:09:19 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.