From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wy0-f175.google.com ([74.125.82.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QzXmT-00076H-5E; Fri, 02 Sep 2011 19:43:53 +0200 Received: by wyf19 with SMTP id 19so2552735wyf.6 for ; Fri, 02 Sep 2011 10:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=a82jcR90U8JmnZlN/rNbUBILHjm2PDFvY6rtQr9ARy4=; b=vulICSlJPn/IGfSiF2NMezktcdxnJ47fe/v16LIF8jZQV8R/njW4N8BFk1VZLDdOuM Oknl0pdT/qWCY2/DIn2IVMJ9xdtLux+ntOX7A3IM4aDGQ6BvZHiknlSV1FySetaCkhxV mlwPx0KVr+wwGSyklQJsE3QZwQ70MuJu1mLlA= MIME-Version: 1.0 Received: by 10.216.207.230 with SMTP id n80mr1320345weo.2.1314985134534; Fri, 02 Sep 2011 10:38:54 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.216.61.208 with HTTP; Fri, 2 Sep 2011 10:38:54 -0700 (PDT) In-Reply-To: <1314982816.5939.616.camel@rex> References: <1314962732.3526.32.camel@mattotaupa> <1314969543.5939.586.camel@rex> <1314976910.3526.36.camel@mattotaupa> <1314982816.5939.616.camel@rex> Date: Fri, 2 Sep 2011 14:38:54 -0300 X-Google-Sender-Auth: rhhH1wB4VldtdgVSgHfXHA7UCLg Message-ID: From: Otavio Salvador To: Patches and discussions about the oe-core layer 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:43:53 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Sep 2, 2011 at 14:00, Richard Purdie wrote: ... >> Hmm, could you please elaborate? > > We all try to find ways to make our workflows more efficient and to do > the best job we can at the things we attempt. The mailing list > separation actively helps me notice the most important things I need to > deal with. Now yes, I could use mail filters, I could do a variety of > things. Even with those I believe my response to various things would be > adversely impacted if we do merge the lists as with the best will in the > world, people sometimes don't do things like tags/prefixes/whatever and > its easier for anyone new to OE to get confused. That is easy to fix since someone might warn the user for how to send this properly. About new users, having multiple mailing lists just makes the problem worse since the user won't know which mailing list to use. So having a single place to ask is much better IMO. --=20 Otavio Salvador=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0O= .S. Systems E-mail: otavio@ossystems.com.br=A0 http://www.ossystems.com.br Mobile: +55 53 9981-7854=A0 =A0 =A0 =A0=A0 =A0 =A0 =A0http://projetos.ossys= tems.com.br From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wy0-f175.google.com ([74.125.82.175]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QzXmT-00076H-5E; Fri, 02 Sep 2011 19:43:53 +0200 Received: by wyf19 with SMTP id 19so2552735wyf.6 for ; Fri, 02 Sep 2011 10:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=a82jcR90U8JmnZlN/rNbUBILHjm2PDFvY6rtQr9ARy4=; b=vulICSlJPn/IGfSiF2NMezktcdxnJ47fe/v16LIF8jZQV8R/njW4N8BFk1VZLDdOuM Oknl0pdT/qWCY2/DIn2IVMJ9xdtLux+ntOX7A3IM4aDGQ6BvZHiknlSV1FySetaCkhxV mlwPx0KVr+wwGSyklQJsE3QZwQ70MuJu1mLlA= MIME-Version: 1.0 Received: by 10.216.207.230 with SMTP id n80mr1320345weo.2.1314985134534; Fri, 02 Sep 2011 10:38:54 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.216.61.208 with HTTP; Fri, 2 Sep 2011 10:38:54 -0700 (PDT) In-Reply-To: <1314982816.5939.616.camel@rex> References: <1314962732.3526.32.camel@mattotaupa> <1314969543.5939.586.camel@rex> <1314976910.3526.36.camel@mattotaupa> <1314982816.5939.616.camel@rex> Date: Fri, 2 Sep 2011 14:38:54 -0300 X-Google-Sender-Auth: rhhH1wB4VldtdgVSgHfXHA7UCLg Message-ID: From: Otavio Salvador To: Patches and discussions about the oe-core layer 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:43:53 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Sep 2, 2011 at 14:00, Richard Purdie wrote: ... >> Hmm, could you please elaborate? > > We all try to find ways to make our workflows more efficient and to do > the best job we can at the things we attempt. The mailing list > separation actively helps me notice the most important things I need to > deal with. Now yes, I could use mail filters, I could do a variety of > things. Even with those I believe my response to various things would be > adversely impacted if we do merge the lists as with the best will in the > world, people sometimes don't do things like tags/prefixes/whatever and > its easier for anyone new to OE to get confused. That is easy to fix since someone might warn the user for how to send this properly. About new users, having multiple mailing lists just makes the problem worse since the user won't know which mailing list to use. So having a single place to ask is much better IMO. --=20 Otavio Salvador=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0O= .S. Systems E-mail: otavio@ossystems.com.br=A0 http://www.ossystems.com.br Mobile: +55 53 9981-7854=A0 =A0 =A0 =A0=A0 =A0 =A0 =A0http://projetos.ossys= tems.com.br