From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QzXsp-0007Ij-TX; Fri, 02 Sep 2011 19:50:28 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p82HjSNr028113; Fri, 2 Sep 2011 18:45:28 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27972-02; Fri, 2 Sep 2011 18:45:24 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p82HjNYt028107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Sep 2011 18:45:23 +0100 From: Richard Purdie To: Patches and discussions about the oe-core layer In-Reply-To: References: <1314962732.3526.32.camel@mattotaupa> <1314969543.5939.586.camel@rex> <89FA71E7-9402-4458-BC9E-42655707B091@dominion.thruhere.net> <1314982026.5939.607.camel@rex> Date: Fri, 02 Sep 2011 18:45:04 +0100 Message-ID: <1314985504.5939.635.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Virus-Scanned: amavisd-new at rpsys.net Cc: openembedded-devel@lists.openembedded.org Subject: Re: [oe] Please merge lists openembedded-devel and openembedded-core again. X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 17:50:28 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2011-09-02 at 14:35 -0300, Otavio Salvador wrote: > On Fri, Sep 2, 2011 at 13:47, Richard Purdie > wrote: > > On Fri, 2011-09-02 at 10:53 -0300, Otavio Salvador wrote: > >> On Fri, Sep 2, 2011 at 10:33, Koen Kooi wrote: > >> > That sounds like people should just subscribe to oe-core if they want to be aware of changes instead of merging the 2 lists. > >> > >> Many times changes are related to meta-oe and oe-core and we'd need to > >> cross-post and seems wrong. > > > > I don't think this is actually true and its reasonable to assume > > discussion on OE-Core is seen by everyone. > > > > You therefore need an OE-Core subscription or both with the latter > > recommended. The benefit is the two lists give some kind of filtering of > > the email topics. > > I am sorry but I disagree. All those affect the layers and thus > changes on oe-core are important to meta-oe so they are all related. > Besides not everyone follow both. I think the expectation is you need to subscribe to OE-Core in all cases and we just need to ensure that expectation is communicated. This also helps people who want to keep up with core changes but aren't interested in the upper layer activities. Asking them to filter out a ton of email on oe-devel simply isn't reasonable. > Personally I've been following mostly oe-core and skipped oe and > someone might be doing the other way around; patch management has > nothing to do with mailing list topic and this we can assume this is > easy to fix using patchwork and proper subject on patches. Having done some patch management myself (at least 4095 patches in the last year) I'll respectfully disagree. Cheers, Richard From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QzXsp-0007Ij-TX; Fri, 02 Sep 2011 19:50:28 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p82HjSNr028113; Fri, 2 Sep 2011 18:45:28 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27972-02; Fri, 2 Sep 2011 18:45:24 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p82HjNYt028107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Sep 2011 18:45:23 +0100 From: Richard Purdie To: Patches and discussions about the oe-core layer In-Reply-To: References: <1314962732.3526.32.camel@mattotaupa> <1314969543.5939.586.camel@rex> <89FA71E7-9402-4458-BC9E-42655707B091@dominion.thruhere.net> <1314982026.5939.607.camel@rex> Date: Fri, 02 Sep 2011 18:45:04 +0100 Message-ID: <1314985504.5939.635.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Virus-Scanned: amavisd-new at rpsys.net Cc: openembedded-devel@lists.openembedded.org Subject: Re: [OE-core] Please merge lists openembedded-devel and openembedded-core again. X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 17:50:28 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2011-09-02 at 14:35 -0300, Otavio Salvador wrote: > On Fri, Sep 2, 2011 at 13:47, Richard Purdie > wrote: > > On Fri, 2011-09-02 at 10:53 -0300, Otavio Salvador wrote: > >> On Fri, Sep 2, 2011 at 10:33, Koen Kooi wrote: > >> > That sounds like people should just subscribe to oe-core if they want to be aware of changes instead of merging the 2 lists. > >> > >> Many times changes are related to meta-oe and oe-core and we'd need to > >> cross-post and seems wrong. > > > > I don't think this is actually true and its reasonable to assume > > discussion on OE-Core is seen by everyone. > > > > You therefore need an OE-Core subscription or both with the latter > > recommended. The benefit is the two lists give some kind of filtering of > > the email topics. > > I am sorry but I disagree. All those affect the layers and thus > changes on oe-core are important to meta-oe so they are all related. > Besides not everyone follow both. I think the expectation is you need to subscribe to OE-Core in all cases and we just need to ensure that expectation is communicated. This also helps people who want to keep up with core changes but aren't interested in the upper layer activities. Asking them to filter out a ton of email on oe-devel simply isn't reasonable. > Personally I've been following mostly oe-core and skipped oe and > someone might be doing the other way around; patch management has > nothing to do with mailing list topic and this we can assume this is > easy to fix using patchwork and proper subject on patches. Having done some patch management myself (at least 4095 patches in the last year) I'll respectfully disagree. Cheers, Richard