[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-18 00:32:59 CEST

On Mon, 2005-10-17 at 18:12 -0400, Greg Hudson wrote:
> On Mon, 2005-10-17 at 08:13 -0400, Daniel Berlin wrote:
> > > You seem to be going from "checking out a
> > > directory would put the directory contents into the specified directory"
> > > to "exporting a file should put the file into the specified directory".
> > Well, yes.
> > And what exactly is wrong with that?
> > Why do you think the case for a single file should be different than the
> > case for a directory when it comes to where we place them?
> Do you understand that "cp -r dir1 dir2" and "cp file dir2" are not
> parallel use cases? The second is shorthand for "cp file dir2/file".

Of course i understand that.

> In one case, the second argument *is* the target path; in the other
> case, the second argument is the *container* for the target path.
> > Do you honestly believe a user expects the cases to behave differently?
> > As a user, it certainly surprised the heck out of me.
> Neither one of us can claim to be a user in the sense which is relevant
> to your argument here; we are both developers with lots of systems
> programming knowledge. Your expectations appear to be biased from
> having used cvs in a particular way.

Actually, i've spoken to quite a few users about this issue, as i
mentioned. Though admittedly, they've all used CVS. It's probably hard
to find a ton of now-subversion users who don't use windows who haven't
used CVS.

> >From what I can tell, in your mental model, exporting a file is
> shorthand for exporting its containing directory but leaving out all the
> other files.

Not quite. I just expect that if i've given it a directory, that it
puts it there, instead of complaining that i've given it a directory.

I would also, BTW, be perfectly satisfied if there was some real way to
tell export where to put things without me having to make the entire
directory structure and copy 3/4ths of the url, continuously.

IE svn export --to-dir=<where> <url>

and have it make "where" (if necessary) and plop the file down there.

> In my model, exporting a single file is like copying the
> file to a designated target path, just like exporting a directory is
> like copying that directory to a designated target path.
As Branko said, we have cat for that. So if that's the real model, IMHO
we should probably just disable export of a single file.
> I think it's important to do things for the right reasons.

So you plan on arguing to make checkout consistent with your model when
we get around to implementing single file checkout?

> You can take that as "I like to argue" if you're locked into those two
> particular options.
Bah. I was sick and frustrated by this behavior, sorry.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 18 00:33:42 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.