Whew. Thanks for the responses, everybody!
Our course w.r.t. issue #933 seems clear: we should keep the 'import'
command, and change its behavior to be like 'cp' (even to the extent
of running the same backend code). But we shouldn't try to add any
vendor branch functionality to import before 1.0, because we've got
enough to do before 1.0 already. At least with the import command
still present, we have the option of adding such functionality later
(though we are not forced to, and can discuss it then).
Sound good?
-K
Eric Gillespie <epg@pretzelnet.org> writes:
> Nuutti Kotivuori <naked@iki.fi> writes:
>
> > This would be my idea as well - make import contain the special
> > hoodlamajik of handling vendor branches, whatever it might need. As a
>
> I don't think import should necessarily be made to create
> branches and tags like cvs's import; remember that there are no
> branches and tags in svn, and i don't want import interfering
> with my chosen repository layout. All i ask is that import do
> the right thing with repeated imports to the same target. Then i
> imagine the procedure being something like this:
>
> svn import foo-1.3 http://example.com/repo/imports/foo/
> svn cp http://example.com/repo/imports/foo/ \
> http://example.com/repo/imports/foo-1.3
> cd foo-wc
> svn merge http://example.com/repo/imports/foo-1.2/ \
> http://example.com/repo/imports/foo-1.3/
>
> --
> Eric Gillespie <*> epg@pretzelnet.org
>
> Build a fire for a man, and he'll be warm for a day. Set a man on
> fire, and he'll be warm for the rest of his life. -Terry Pratchett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 23 05:14:45 2002