I agree, here, with Joe. Wondering if it's an appropriate alternative. I'm facing similar, with a subproject entering incubation, and I'd like to know our decision here, before I go and create a subproject structure under /httpd/ that turns out to be wonky.
is /trunk/httpd/ an appropriate solution? This bit me, trying to check out some /incubation/ stuff. Bill At 09:32 AM 6/7/2004, Joe Schaefer wrote: >Bill Stoddard <[EMAIL PROTECTED]> writes: > >> Brian W. Fitzpatrick wrote: >> > On Jun 6, 2004, at 10:42 PM, Geoffrey Young wrote: >> > >> >> >> >>> FYI, Fitz did a conversion of apache-1.3, which is now located at >> >>> http://svn.apache.org/repos/test/httpd/. (in the test repository). >> >> >> >> >> >> wow, that's a lot of data - 10 minutes later and I'm still downloading... >> > Wait! No! You don't want to check out >> > http://svn.apache.org/repos/test/httpd/ ... you want to check out >> > http://svn.apache.org/repos/test/httpd/trunk/ >> > By checking out http://svn.apache.org/repos/test/httpd/, you're >> > getting one copy of the httpd source tree for every branch and tag! >> >That's a LOT of data! >> >> This is going to be a recurring problem. Geoff did the intuitive >> thing, which turned out to be wrong. Not good. > >I think the other repository layout, with eg /trunk/httpd instead of >/httpd/trunk, prevents this problem since the intuitive thing >would yield a 404. > > >-- >Joe Schaefer
