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

a couple observations about doing "svn import"

From: Robert P. J. Day <rpjday_at_mindspring.com>
Date: 2005-01-06 20:34:04 CET

  first, something i meant to mention a while back when i was getting
started. it might be worth it, when explaining "svn import", to
*really* emphasize that, when you import a directory, what is actually
being imported is the recursive *contents* of that directory. so
that, if i have a directory structure of the form:


and i do

  $ svn import dir URL

what i'll get is


if you read the book closely enough, you will eventually realize that,
but beginners may very well expect to see "dir" being added to the
repository. and if they really want to do that, they should run:

  $ svn import dir URL/dir

i realize that's nitpicky, but i got burned by that the first time i
tried it, and the book doesn't go out of its way to make that clear.

  second, i realize that, if i want to start a new "project" with all
of trunk/, branches/ and tags/, it's easiest if i first create the
entire structure ahead of time and do a single import, so that it
appears as a single revision.

  but given that this is not always possible and that i might have to
add a new "project" in bits and pieces, i assume that the natural way
to do that is just with a series of "svn import"s (and, optionally,
"svn mkdir"s). the drawback, of course, is that each operation counts
as a separate revision but i assume, in some cases, that can't be


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 6 20:39:38 2005

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.