That's fine, I wasn't really hung up on one way or the other. It makes sense to do it the way you have it, so let's leave it.
I assume builds would have their own dir? How do you want to do the import, since we are currently using cvs on sf.net? History? -----Original Message----- From: William A. Rowe, Jr. <[EMAIL PROTECTED]> To: [email protected] <[email protected]> Sent: Wed Mar 15 18:07:15 2006 Subject: Re: Quick announcement I created it the other way for the following reason... /repos/asf/incubator/lokahi/site/... we aren't likely to even tag this - generally we sync the website to trunk, unless someone decides to do a site refactoring. Certainly the 'state of the site' doesn't matter when rolling a project tarball. /repos/asf/incubator/lokahi/lokahi/... could have been named source, but here would sit the first lokahi main tree, at /repos/asf/incubator/lokahi/lokahi/trunk (which is where the initial import would occur.) Anything going into our tarball would fall into lokahi/lokahi/trunk. Anything that doesn't 'fit', the website, status files, whatever, can all be deposited under their own (new) trees. Take a look at https://svn.apache.org/repos/asf/incubator/lokahi/... and if you prefer - we can rearrange. Just waiting for an ack of the account creation requests at this point, and we can start loading code. Bill drtobes wrote: >> trunk/ >> branches/ >> tags/ >> >>directly under the top level > > > > > This makes the most sense to me. > > Steve > ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. ------------------------------------------------------------------------------
