All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Please merge lists openembedded-devel and openembedded-core again.
Date: Fri, 2 Sep 2011 14:38:54 -0300	[thread overview]
Message-ID: <CAP9ODKrevY3MhiTckzroNY6XN_rpj4rcwGRg_aBehkXO6+YcsQ@mail.gmail.com> (raw)
In-Reply-To: <1314982816.5939.616.camel@rex>

On Fri, Sep 2, 2011 at 14:00, Richard Purdie <rpurdie@rpsys.net> 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.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



WARNING: multiple messages have this Message-ID (diff)
From: Otavio Salvador <otavio@ossystems.com.br>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] Please merge lists openembedded-devel and openembedded-core again.
Date: Fri, 2 Sep 2011 14:38:54 -0300	[thread overview]
Message-ID: <CAP9ODKrevY3MhiTckzroNY6XN_rpj4rcwGRg_aBehkXO6+YcsQ@mail.gmail.com> (raw)
In-Reply-To: <1314982816.5939.616.camel@rex>

On Fri, Sep 2, 2011 at 14:00, Richard Purdie <rpurdie@rpsys.net> 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.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



  reply	other threads:[~2011-09-02 17:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02 11:25 Please merge lists openembedded-devel and openembedded-core again Paul Menzel
2011-09-02 13:05 ` [oe] " Otavio Salvador
2011-09-02 13:05   ` Otavio Salvador
2011-09-02 13:19   ` [oe] " Richard Purdie
2011-09-02 13:19     ` [OE-core] " Richard Purdie
2011-09-02 13:23     ` [oe] " Otavio Salvador
2011-09-02 13:23       ` [OE-core] " Otavio Salvador
2011-09-02 13:33       ` [oe] " Koen Kooi
2011-09-02 13:33         ` [OE-core] " Koen Kooi
2011-09-02 13:53         ` [oe] " Otavio Salvador
2011-09-02 13:53           ` [OE-core] " Otavio Salvador
2011-09-02 16:47           ` [oe] " Richard Purdie
2011-09-02 16:47             ` [OE-core] " Richard Purdie
2011-09-02 17:35             ` [oe] " Otavio Salvador
2011-09-02 17:35               ` [OE-core] " Otavio Salvador
2011-09-02 17:45               ` [oe] " Richard Purdie
2011-09-02 17:45                 ` [OE-core] " Richard Purdie
2011-09-03 17:36             ` Detlef Vollmann
2011-09-02 15:21     ` Paul Menzel
2011-09-02 17:00       ` [oe] " Richard Purdie
2011-09-02 17:00         ` [OE-core] " Richard Purdie
2011-09-02 17:38         ` Otavio Salvador [this message]
2011-09-02 17:38           ` Otavio Salvador
2011-09-02 20:18         ` Paul Menzel
2011-09-02 20:51           ` Andreas Müller
2011-09-02 18:48       ` [oe] " Phil Blundell
2011-09-02 18:48         ` [OE-core] " Phil Blundell
2011-09-02 19:29         ` Andreas Müller
2011-09-02 21:34           ` Koen Kooi
2011-09-02 21:49             ` Paul Menzel
2011-09-03  7:08               ` Martin Jansa
2011-09-03  7:30               ` Eric Bénard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP9ODKrevY3MhiTckzroNY6XN_rpj4rcwGRg_aBehkXO6+YcsQ@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.