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

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> 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).

Sounds like a good plan to me.

--
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
Received on Wed Oct 23 06:46:09 2002