You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Brass Tilde <br...@insightbb.com> on 2004/11/19 02:12:46 UTC
Repository organization
OK, I'm reading through "The Book", in Chapter 3, and I thought the
recommended directory structure in a repository with multiple projects would
look something like this:
/trunk/proj1
/trunk/proj2
/trunk/proj3
/branches/proj1
/branches/proj2
/branches/proj3
/tags/proj1
/tags/proj2
/tags/proj3
However, later on, I begin to understand that maybe it's supposed to look
like this:
proj1/trunk
proj1/tags
proj1/branches
proj2/trunk
proj2/tags
proj2/branches
proj3/trunk
proj3/tags
proj3/branches
Which makes considerably more sense to me.
Which one is the intended recommended structure?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository organization
Posted by v4r4n <co...@gmail.com>.
Ultimately it is entirely up to you.
It doesn't really matter to subversion, but I'd go with the 2nd choice
just because it would be easier to move around, copy, or remove all of
proj1, or proj3, if need be.
On Thu, 18 Nov 2004 21:12:46 -0500, Brass Tilde
<br...@insightbb.com> wrote:
> OK, I'm reading through "The Book", in Chapter 3, and I thought the
> recommended directory structure in a repository with multiple projects would
> look something like this:
>
> /trunk/proj1
> /trunk/proj2
> /trunk/proj3
> /branches/proj1
> /branches/proj2
> /branches/proj3
> /tags/proj1
> /tags/proj2
> /tags/proj3
>
> However, later on, I begin to understand that maybe it's supposed to look
> like this:
>
> proj1/trunk
> proj1/tags
> proj1/branches
> proj2/trunk
> proj2/tags
> proj2/branches
> proj3/trunk
> proj3/tags
> proj3/branches
>
> Which makes considerably more sense to me.
>
> Which one is the intended recommended structure?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: I can't see content of revisions of moved project by using subclipse.
Posted by Ben Collins-Sussman <su...@collab.net>.
Subclipse is a separate project. Please repost to
users@subclipse.tigris.org.
(And why did you quote an unrelated email, and change the subject?
It's a bit confusing. :-) )
On Nov 20, 2004, at 7:42 AM, Taner Diler wrote:
> Hi,
>
> I have a question about moving proccess and subclipse.
>
> I moved a project to top folder in repository and I checkouted moved
> project by using subclipse. Then I wanted to compare a java file in
> working copy with previous repository version. I can see all revision
> numbers but when I open a previous revision, revision content comes
> empty in subclipse screen. But, when I use "svn diff -r HEAD:...",
> everthing is okay.
>
> Before moving proccess, I could see content of all revisions by using
> subclipse.
>
>
> .
>
>
>
>
>
> ----- Original Message ----- From: "Ben Collins-Sussman"
> <su...@collab.net>
> To: "Brass Tilde" <br...@insightbb.com>
> Cc: <us...@subversion.tigris.org>
> Sent: Friday, November 19, 2004 9:00 PM
> Subject: Re: Repository organization
>
>
>> >
>>> I phrased that poorly. When I read the Introduction, I was under the
>>> impression the recommended structure was as above; reading Chapter 3
>>> changed
>>> my mind.
>>
>> Yah, as you'll see in chapter 5, the convention is to create what we
>> call a "project root":
>>
>> project/trunk
>> project/branches
>> project/tags
>>
>> The thing is, it's up to you to decide where the "root" is. If your
>> repository only contains one project, it could be the "/" dir of the
>> repository. (That's what the chapter 1 demo is doing.) If your
>> repository has lots of projects, then project-roots could be
>> scattered all over the place within it.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
I can't see content of revisions of moved project by using subclipse.
Posted by Taner Diler <ta...@riskturk.com>.
Hi,
I have a question about moving proccess and subclipse.
I moved a project to top folder in repository and I checkouted moved project
by using subclipse. Then I wanted to compare a java file in working copy
with previous repository version. I can see all revision numbers but when I
open a previous revision, revision content comes empty in subclipse screen.
But, when I use "svn diff -r HEAD:...", everthing is okay.
Before moving proccess, I could see content of all revisions by using
subclipse.
.
----- Original Message -----
From: "Ben Collins-Sussman" <su...@collab.net>
To: "Brass Tilde" <br...@insightbb.com>
Cc: <us...@subversion.tigris.org>
Sent: Friday, November 19, 2004 9:00 PM
Subject: Re: Repository organization
> >
>> I phrased that poorly. When I read the Introduction, I was under the
>> impression the recommended structure was as above; reading Chapter 3
>> changed
>> my mind.
>
> Yah, as you'll see in chapter 5, the convention is to create what we call
> a "project root":
>
> project/trunk
> project/branches
> project/tags
>
> The thing is, it's up to you to decide where the "root" is. If your
> repository only contains one project, it could be the "/" dir of the
> repository. (That's what the chapter 1 demo is doing.) If your
> repository has lots of projects, then project-roots could be scattered all
> over the place within it.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository organization
Posted by Brass Tilde <br...@insightbb.com>.
> > I phrased that poorly. When I read the Introduction, I was under the
> > impression the recommended structure was as above; reading Chapter 3
> > changed my mind.
>
> Yah, as you'll see in chapter 5, the convention is to create what we
> call a "project root":
Whoa! Not so fast, I just finished Chapter 3! :-)
Seriously, I'll probably be rereading Chapter 3 again over the weekend and
experimenting based on my new-found understanding. I really *am* slow at
picking this stuff up sometimes, so it helps to reiterate through it.
> project/trunk
> project/branches
> project/tags
>
> The thing is, it's up to you to decide where the "root" is. If your
And that's why I was confused. Your structure above makes much more sense
to me, and my incomplete understanding of the structure presented by the
Introduction example was getting in the way of learning about SVN. Now that
I'm past it, hopefully it will go faster.
Brad
> repository only contains one project, it could be the "/" dir of the
> repository. (That's what the chapter 1 demo is doing.) If your
> repository has lots of projects, then project-roots could be scattered
> all over the place within it.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository organization
Posted by Ben Collins-Sussman <su...@collab.net>.
>
> I phrased that poorly. When I read the Introduction, I was under the
> impression the recommended structure was as above; reading Chapter 3
> changed
> my mind.
Yah, as you'll see in chapter 5, the convention is to create what we
call a "project root":
project/trunk
project/branches
project/tags
The thing is, it's up to you to decide where the "root" is. If your
repository only contains one project, it could be the "/" dir of the
repository. (That's what the chapter 1 demo is doing.) If your
repository has lots of projects, then project-roots could be scattered
all over the place within it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository organization
Posted by Brass Tilde <br...@insightbb.com>.
> > OK, I'm reading through "The Book", in Chapter 3, and I thought the
> > recommended directory structure in a repository with multiple projects
> > would look something like this:
> >
> > /trunk/proj1
> > /branches/proj1
> > /tags/proj1
> What in chapter 3 gave you that impression? I just glanced through it,
> and don't see why you'd get that idea.
I phrased that poorly. When I read the Introduction, I was under the
impression the recommended structure was as above; reading Chapter 3 changed
my mind.
Why? If execute the instructions in the Introduction (Rev 11176M, Page 6)
to create and populate a new repository on Win2K SP4 using SVN 1.1.1 (client
and server):
:: Some setup
md \path\to
md \tmp\project\branches
md \tmp\project\tags
md \tmp\project\trunk
echo something > \tmp\project\trunk\foo.c
echo else > \tmp\project\trunk\bar.c
echo entirely > \tmp\project\trunk\makefile
:: commands from "the book"
svnadmin create /path/to/repos --fs-type fsfs
svn import /tmp/project file:///path/to/repos -m "initial import"
and then execute "svn list file:///path/to/repos -v -R" on that repository,
I get the following:
1 Brad Nov 19 13:21 branches/
1 Brad Nov 19 13:21 tags/
1 Brad Nov 19 13:21 trunk/
1 Brad 12 Nov 19 13:21 trunk/bar.c
1 Brad 12 Nov 19 13:21 trunk/foo.c
1 Brad 12 Nov 19 13:21 trunk/makefile
In this simple example, everything is directly off the root of the
repository. I recklessly let this color everything else I was reading until
I started seeing other examples (the collab.net SVN repository, primarily)
where the project name appeared before "trunk".
More experimentation showed that appending the project name to the
repository, when importing, ala:
svn import /tmp/project file:///path/to/repos/proj1 -m "initial import"
creates the project in another directory off the root, which makes much more
sense to me.
Yes, I'm slow on the pickup sometimes, but I'll probably get it eventually.
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository organization
Posted by Ben Collins-Sussman <su...@collab.net>.
On Nov 18, 2004, at 8:12 PM, Brass Tilde wrote:
> OK, I'm reading through "The Book", in Chapter 3, and I thought the
> recommended directory structure in a repository with multiple projects
> would
> look something like this:
>
> /trunk/proj1
> /trunk/proj2
> /trunk/proj3
> /branches/proj1
> /branches/proj2
> /branches/proj3
> /tags/proj1
> /tags/proj2
> /tags/proj3
>
What in chapter 3 gave you that impression? I just glanced through it,
and don't see why you'd get that idea.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org