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

Re: How come the import cmnd doesn't work?

From: Aaron Montgomery <eeyore_at_monsterworks.com>
Date: 2006-03-08 19:19:18 CET

On Mar 8, 2006, at 9:44 AM, Res Pons wrote:

> However, what does NOT make sense is the SVN .pdf manual on page 6
> "A Quick Start" indicating MISLEADINGLY that the 'import' commnad
> will automatically create these subdirs. Am I misunderstanding the
> manual, have I misread something?

I think you are misreading. On page 6, the manual says "Next, create
a tree of files and directories to import into the repository, your
structure should contain three top-level directories named branches,
tags, and trunk..." so it is saying that you need to create these
directories in your local copy before you run svn import.

> Just for the sake of consistency, I wish SVN automatically did this
> for every project w/o users resorting to their own hacks and scripts.

Please no. It is quite possible that I want a different layout (e.g.,
having each project in its own top level directory and tags,
branches, trunk directories under each project directory) or maybe I
prefer to call the "tags" directory by the name "releases", or
perhaps I prefer to avoid English completely and want to name them
the equivalent names in Klingon (far fetched, but wanting the names
in French or German isn't as far fetched). Since svn doesn't attach
any special meaning to them (except by convention of its users), svn
should let the user decide what they are to be called or if they are
to be created at all. You can always create them later if you
discover you forgot to create them on the first import.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 8 19:24:25 2006

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