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

Re: Making import syntax consistant with mv, cp, export

From: Noel Yap <yap_noel_at_yahoo.com>
Date: 2002-10-23 14:51:55 CEST

--- Branko Čibej <brane@xbc.nu> wrote:
> >If we're "making" people wrap svn to have "branch"
> and
> >"label" commands, we might as well make them do the
> >same for "import" and "export" commands.
> >
> >
> Oh come on, we're not making people do anything;
> you're the one who
> insists on forcing a ClearCase-like usage model onto
> Subversion.
> Subversion is not ClearCase, it has a different
> metamodel, and it will
> stay that way. Live with it.

I didn't mean forcing a particular model at all. Nor
did I ever propose that Subversion can emulate the
ClearCase metamodel. My prior email was to get a
ClearCase-like repository structure in which the
branch hierarchy was directly represented by the
directory hierarchy. It's completely possible to have
this in Subversion. I felt from other posts that
different repository structures were welcome. Aren't
you working on a slovenian one? :-)

I had put "making" in quotes to mean that users will
probably want separate commands for creating branches,
labels, and copies even though they are exactly the
same operation.

As an aside, within a ClearCase-like repo structure,
the meaning of "make a branch" is different from "cp"
since it'll encompass "mkdir" and "cp". To make
myself clear to everyone, I'm not proposing that
Subversion create such a semantic. I also think I'm
completely free to wrap svn (or even create a new
client) to support such a semantic.

Noel

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 23 14:52:36 2002

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.