[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: Eric Gillespie <epg_at_pretzelnet.org>
Date: 2002-10-22 23:27:21 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> 3. An 'import' is usually a one-time special event. The concept is
> friendly to CVS users, which is important. I don't want

No, the import command is *not* friendly to cvs users. The cvs
import command is used to maintain third-party sources, not just
for initially populating your repository. I would go so far as
to say that is the most common usage (it is certainly the
predominant reason for *my* usage of import). svn import,
however, is useless for that function; it bombs when you try to
import to the same path again. That is why the section of the
handbook about creating vendor branches (which i originally
wrote) describes such a convoluted process.

What i want to see is the import command made useful for
maintaining third-party sources, not removed entirely.

--
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 Tue Oct 22 23:28:03 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.