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

Re: I hate "svn help import"

From: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2007-01-05 16:47:34 CET

This comment is tangental to your suggestion for better 'svn help
import' wording, but I have, in 3+ years of using SVN to manage many
projects and vendor branches, never once in my life used the "import"
command. IMO an in-place Add is simply better because you get to see
exactly what you'll get *before* commiting. You can always 'svn co -N'
if you want a sparse tree to add into.


Kenneth Porter wrote:
> "svn import" bites me every time I use it. Today, I wanted to import the
> source tree for wxWidgets into my vendor tree. So I run wxMSW-2.8.0.exe
> to install it to d:\devel\wxWidgets-2.8.0. I cd to d:\devel and run:
> cd d:\devel
> svn import https://myserver/myrepo/vendor wxWidgets-2.8.0 -m "Import
> wxWidgets-2.8.0."
> When it completes, I discover that instead of acting like "svn add"
> (which would have put everything under a new wxWidgets-2.8.0
> subdirectory in the repo) it's dumped everything that was in that
> directory into my vendor directory in the repo. Ugh. Now I have to go
> clean it up.
> Perhaps someone could suggest better wording for "svn help import" that
> would keep me from making this mistake again in 6 months.
> Here's what's there now:
> If PATH is a directory, the contents of the directory are added
> directly under URL.
> I'd suggest a parenthetic caution:
> If PATH is a directory, the contents of the directory (not the
> directory itself)
> are added directly under URL.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 5 16:44:40 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.