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

Re: Help Needed w/Subversions Weird Repository Layout

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-11 19:16:46 CET

On Mar 11, 2005, at 12:03 PM, Craig A. Vanderborgh wrote:

> Hello Again:
> First, thanks to Gary, David, and Ben for the input. I do appreciate
> that Subversion does not place any hard and fast requirements on how
> repositories are laid out. On the other hand, it is clear that you
> can really cause yourself a lot of trouble by making bad choices at
> the set-up stage. Your advice will prevent that from happening.

Not true. If you don't like your layout, just rearrange the tree with
'svn mv URL1 URL2'. This isn't CVS. :-)

> What I was really after (thank you, Gary) is figuring out the intended
> or "canonical" way of setting up repositories. Gary's suggestion is
> what I was looking for. I found something else of great help that I
> wanted to point out for other people in my situation.
> The GCC project itself is now using Subversion for its VCS,

Actually, it's not. It's *preparing* to do so, after the next release.
  That wiki is part of the preparation; it's still using a test server
for experimentation.

> and it has an extremely helpful Wiki that covers something the book
> leaves out - use of Subversion for the case of a large-ish "real
> world" project. We found this extremely helpful, and the Subversion
> people might want to refer to this on the site:
> http://gcc.gnu.org/wiki/SvnHelp
> By the way, kudos to the Subversion developers - having the GCC
> project as a Subversion "user" is clearly quite an achievement!!

Also Apache, Samba, Mono, and others. You should look at the
propaganda page:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 11 19:19:15 2005

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

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