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

Re: project folders

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-12-18 10:04:47 CET

Little Prince wrote:
> I just started looking at TortoiseSVN 1.4.5 for Windows. When I add a
> new project, why isn't the project saved in subversion using the name
> of the project folder? I should be able to right click on the folder
> and import it into svn. Not have to provide the project folder name.

Because the default and recommended folder layout is
/trunk
/branches
/tags
and then you import your project directly to /trunk, *without* a
directory for the project itself (the trunk usually *is* the project
folder).

> Also when I select a project to check out, I would like to turn off
> those annoying dialog boxes that tells me that my current folder is
> not empty, or some folder doesn't exist. The GUI should be smart
> enough to create the new folder, and then place the content of the
> project into that folder. What end up happening is that the project
> folder doesn't get created, and all the files simply get checkout
> into the current folder. Totally not what I want or expect.

That's a problem only if you've used TortoiseCVS before. But users who
haven't like the way TSVN works much better. And you wouldn't end up
with all the files in the current folder if you wouldn't have ignored
the warning that your current folder is not empty.

> The behaviour is unintuitive, and unlike what I am use to with
> Tortoise CVS. Also at one point I was able to "add the new project

I disagree. TSVN is very intuitive.

> folder" and then commit them it, I tired it another time and all I
> was able to select was import. Things like this drive me nuts, having
> functionality I need only not be see it the next time I want to use
> it. With import, I can't ommit any files I don't want in Subversion.

I'm absolutely sure that you will get into much more troubles. Because
you're trying to use the same workflows for svn as you did for CVS
(creating project folders is just one indicator). But by doing so,
you're ignoring the fact that svn *is not* cvs.

I recommend you read the Subversion book
http://svnbook.red-bean.com/
first to get a little bit familiar on how svn works and where/why it
differs from cvs.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Dec 18 10:04:58 2007

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

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