Ok I misread then, it was kinda of misleading or not clear to me. My
The 2nd part of your response made me laugh but I guess you're right.
Somehow, I assumed everyone's going to use SVN in English. :)
----Original Message Follows----
From: Aaron Montgomery <firstname.lastname@example.org>
To: Subversion mailing list <email@example.com>
CC: Res Pons <firstname.lastname@example.org>
Subject: Re: How come the import cmnd doesn't work?
Date: Wed, 8 Mar 2006 10:19:18 -0800
MIME-Version: 1.0 (Apple Message framework v746.2)
Received: from out4.smtp.messagingengine.com ([18.104.22.168]) by
bay0-mc12-f13.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 8
Mar 2006 10:19:22 -0800
Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149])by
frontend1.messagingengine.com (Postfix) with ESMTP id 04C8DD3B118;Wed, 8
Mar 2006 13:19:22 -0500 (EST)
Received: from frontend2.messagingengine.com ([10.202.2.151]) by
frontend1.internal (MEProxy); Wed, 08 Mar 2006 13:19:22 -0500
Received: from [22.214.171.124] (mac81181.d.cwu.edu [126.96.36.199])by
frontend2.messagingengine.com (Postfix) with ESMTP id 8D52558072B;Wed, 8
Mar 2006 13:19:20 -0500 (EST)
X-Sasl-enc: Hd1c8odpO3sq30MLfT+IUXngCY1r7cxZA/T8pPi0lSgt 1141841960
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 08 Mar 2006 18:19:23.0184 (UTC)
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.
Express yourself instantly with MSN Messenger! Download today - it's FREE!
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Mar 8 21:34:23 2006