<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>On 2007-06-30, at 18:36, Reid Spencer wrote:</div><div><br class="webkit-block-placeholder"></div><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span class="Apple-style-span" style="-webkit-text-stroke-width: -1; ">I'm finding the current layout a bit frustrating, not to mention that it breaks all the documentation. [...] I would rather see it laid out like this:</span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "></div></blockquote></blockquote><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> trunk/llvm/...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> trunk/stacker/...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> trunk/java/...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> branches/llvm/...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> branches/stacker/...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> branches/java/...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> tags/llvm/...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> tags/stacker/...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "> tags/java/..</div></blockquote><div><br class="webkit-block-placeholder"></div><div>Reid,<div><br class="webkit-block-placeholder"></div><div>This is a common problem with Subversion. I wouldn't recommend using the layout you suggested here, though. Although it's "just" a convention, <i>please</i> keep the standard layout at the root of each project. (You're proposing interceding a directory layer between trunk, branches, and tags, etc. I don't think you'll find that it solves many management problems.)</div><div><div><br class="webkit-block-placeholder"></div><div>If the projects are too granular, merge them together. It might, in fact, be appropriate to use a single project root for the totality of llvm. Getting this correct is by far the most important decision to be made, IMO. It's very easy to check out a subdirectory of a project, but much harder to check out a union of several projects.<div><br class="webkit-block-placeholder"></div><div>However, if a union of several projects is necessary, Subversion does have an svn:external property[1] which can be used to create precisely that. It's <i>much</i> more complicated to tag or branch such a beast, however, so it is strongly recommended that such a thing <i>not</i> be used as a unit of release.</div><div><br class="webkit-block-placeholder"></div><div>Anton, as Reid mentioned, there's absolutely no need to worry about wasting repository space with copies. However, since copies are so incredibly cheap on the server, there <i>is</i> a need to worry about wasting developer hard disk space. At the client, copies are much more expensive with Subversion than with CVS, so your intuition is still very useful.</div><div><br></div><div>— Gordon<br><div><div><br class="webkit-block-placeholder"></div><div><div>[1] <a href="http://svnbook.red-bean.com/en/1.0/ch07s03.html">http://svnbook.red-bean.com/en/1.0/ch07s03.html</a></div><br></div></div></div></div></div></div></body></html>