Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 60430 invoked from network); 23 Jan 2007 14:04:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jan 2007 14:04:22 -0000 Received: (qmail 56302 invoked by uid 500); 23 Jan 2007 14:04:22 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 56266 invoked by uid 500); 23 Jan 2007 14:04:22 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 56254 invoked by uid 99); 23 Jan 2007 14:04:22 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2007 06:04:22 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of andrey.yakushev@gmail.com designates 64.233.182.184 as permitted sender) Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2007 06:04:13 -0800 Received: by nf-out-0910.google.com with SMTP id a4so248069nfc for ; Tue, 23 Jan 2007 06:03:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lqV0/AwCif5wEAC4e4pIRKFS6Uewlh5K889OZr/yaM8uHUPgbfk+h4w66kQcLpDVv8GAuKWaVxivtoWn5rrBCHHPw7p2zuN5Bemt5GzWGKqEY++YWjsHTSOxJg7J70CRnHSp4v+MsJm+NJOREdelURAL9+G89+yICF6tO/xJaVM= Received: by 10.82.138.6 with SMTP id l6mr6313078bud.1169561031894; Tue, 23 Jan 2007 06:03:51 -0800 (PST) Received: by 10.82.100.20 with HTTP; Tue, 23 Jan 2007 06:03:51 -0800 (PST) Message-ID: <3c7e1c080701230603p7267498bs1e0358f385746a5@mail.gmail.com> Date: Tue, 23 Jan 2007 17:03:51 +0300 From: "Andrey Yakushev" To: dev@harmony.apache.org Subject: Re: [drlvm][doc] duplicated thread manager doc in svn source tree In-Reply-To: <523F3D8D8C97554AA47E53DF1A05466A92D7C4@nnsmsx411.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3c7e1c080701230241w7042d398kc2739a8c37e5912f@mail.gmail.com> <523F3D8D8C97554AA47E53DF1A05466A92D7C4@nnsmsx411.ccr.corp.intel.com> X-Virus-Checked: Checked by ClamAV on apache.org Nadya, I prefer seIf-documented sources and so I consider files with DRLVM documentation /harmony/standard/site/docs/subcomponents/drlvm virtually placed somewhere in /harmony/enhanced/drlvm/trunk/.../doc with obvious reasons why it is not such currently. In other words doc files should be moved thus if we ever prepared mixed source and doc bundle. So current state is good enough for me. :) Thanks, Andrey On 1/23/07, Morozova, Nadezhda wrote: > Andrey, > And what about the documents on the website? > > Cheers, > Nadya > > >-----Original Message----- > >From: Andrey Yakushev [mailto:andrey.yakushev@gmail.com] > >Sent: Tuesday, January 23, 2007 1:41 PM > >To: dev@harmony.apache.org > >Subject: Re: [drlvm][doc] duplicated thread manager doc in svn source > tree > > > >I think we definitely should get rid of documents duplication. So I > >agree with these files removing at present. > > > >As for vm/thread/doc directory, it can exist and contain component > >implementation specific docs. If we ever have another TM > >implementation it can have another impl peculiarities in > >vm/thread_v2/doc. > > > >vm/doc ideally should contain generic description of VM as a set of > >standard associated components. But it can happen sometimes in future, > >because current docs usually combines interface and implementation > >description. > > > >Thanks, > >Andrey > > > > > >On 1/19/07, Morozova, Nadezhda wrote: > >> Hi, > >> I've discovered that the vm/thread/ directory has the doc/ > subdirectory > >> with the thread manager description and supporting files. > >> I suggest that we remove that directory with all its contents > because: > >> * all relevant docs are stored on the site, including the thread > manager > >> doc (with the correct css and all) > >> * if not on the site, docs might exist in vm/doc directory, not in > >> directories of subcomponents. > >> This way, we can be sure no stray doc copies appear. > >> > >> Opinions? Suggestions? > >> > >> Thanks, > >> Nadya Morozova > >> >