Re: multiple "svn import" behavior

I don't have a big problem with your notion of imports (I like the idea
that import either creates or replaces the target directory in the
repository, perhaps unless you give it a flag to preserve old files and
directories), but I think you might have some misconceptions about
Subversion which impact your proposed syntax.

Mainly: Subversion doesn't have branches and tags like CVS has.
Subversion merely provides cheap directory copies. If you want to
preserve the state of a directory before you make changes, copy the
directory and set the acl so it's read-only. If you want to branch
development of a directory, make a copy and modify both copies separately.

So there is no "svn tag" command, and your "-tag" option to "svn import"
doesn't make sense.

Before you ask, we haven't decided how merges will work yet, or how merge
history will be maintained.

(Also, long options use the syntax "--foo", not "-foo". So it would be
--tag, not -tag, if that option made sense.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:56 2006