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

Re: cmd line stuff (was: CVS update: ...)

From: Jim Blandy <jimb_at_savonarola.red-bean.com>
Date: 2000-10-17 20:26:07 CEST

I've added my old command-line notes to subversion/client/README. Here
are the ideas I thought were worthwhile:

* It seems kind of archaic to type:

   svn -d REPO-SPEC checkout MODULE

This splits the information `what am I checking out' across two
different places. It would be nicer to simply name the thing you're
checking out, using some appropriate noun clause. For remote things,
URL's are the natural kind of noun clause:

   svn checkout http://subversion.tigris.org/repo/subversion

I don't know if this is exactly the DAV way; maybe Greg can provide a
more realistic example. But the important idea is that the syntax
should be:

   svn checkout THING

* Given Subversion's idea that the repository is just a versioned
filesystem, it makes sense to allow some operations directly on the
repository. For example, if I want to copy a tree, so I can start
work on a separate branch of development, I shouldn't have to check
out this huge tree, copy a big section of it, and then commit that.

Just as I can say:

   svn cp SOURCE DEST

to copy something in my working directory, I should be able to use
URL's for SOURCE and / or DEST, and have the right thing happen. It's
the same idea behind rcp / scp: instead of providing one command for
downloading, and a separate command for uploading, just provide a
syntax for referring to files elsewhere, and let the names tell you
how the data needs to flow.

Since we don't support inter-repository branching yet, we would
require for now that when SOURCE or DEST are remote, they must refer
to the same repository.
Received on Sat Oct 21 14:36:11 2006

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.