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

RE: Repository Layout - One Vs. Many

From: Crucius, Wesley <WCrucius_at_sandc.com>
Date: 2004-03-25 18:22:50 CET

>Why are you checking out all of the tags? Normally you simply check
out
>the trunk of the repository or one specific tag, not all 200 of them.
>
>If your repository looks like this:
>
>/trunk/
>/tags/
>/tags/foo-1.0
>/tags/foo-1.1
>/tags/foo-1.2
>
>You would check out the /trunk portion of it, and ONLY that. When you
>want a specific version check that out, but don't check out the top
>level of the tree or the tags directory, that's a HUGE amount of data
>you're putting on your local disk for no reason.
>
>-garrett

Convenience (update on projects parent folder is the simplest way to get
the whole repository structure and "get latest" revisions), but I can
see now why that's a bad thing to do because it forces me to get all the
tagged versions too! Maybe the other recommeded hierarchy makes more
sense for me?

Meaning, use this:

SVNWork\trunk\project1\
             \project2\
             \projectN\
SVNWork\tags\project1\
            \project2\
            \projectN\
SVNWork\branches\project1\
                \project2\
                \projectN\

Instead of this:

SVNWork\project1\trunk
                \tags
                \branches
SVNWork\project2\trunk
                \tags
                \branches
SVNWork\projectN\trunk
                \tags
                \branches

Thanks for the feedback, this is starting to clear things up!

Wes

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 18:25:54 2004

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