[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: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-10-18 19:55:07 CEST

On Mon, 2005-10-17 at 22:32 -0400, Daniel Berlin wrote:
> > So you plan on arguing to make checkout consistent with your model when
> > we get around to implementing single file checkout?
> I ask this, btw, because the current mantra i hear is "export is
> checkout without producing the .svn dirs"
> If this is what we are going to tell people, we should prepared to stick
> with it (IE decide what both are going to do with single files in some
> consistent way), or stop saying it.

I honestly don't know.

I observe that my model is already what we've implemented (though
apparently we haven't documented it), so changing to your model has
compatibility issues.

One possibility is that we might never support checking out a single
file because we can't support it quite right. Or at least, not until
such a day as we have a second working copy model which doesn't use a
hidden-metadata-directory approach. A possible workaround for users
wanting to check out a single file is "svn co --depth=0 dir-url; cd dir;
svn up file", which generalizes to checking out two or three specific
files as well. (This is assuming a future where we have proper --depth
support and better non-recursive checkout handling.)

Incidentally, earlier you said that the "export as copy" mental model is
pointless for files because users can "svn cat file-url > file". (Does
that mean that cp is pointless for files?) I'll note that such an
approach does not obey the svn:executable property.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 18 19:57:29 2005

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

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