From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: call for participation on openembedded-users mailing list
Date: Sun, 19 Jun 2011 10:50:52 +0200 [thread overview]
Message-ID: <itkd9c$657$1@dough.gmane.org> (raw)
In-Reply-To: <201106171537.06113.paul.eggleton@linux.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17-06-11 16:37, Paul Eggleton wrote:
> On Friday 17 June 2011 15:28:56 Koen Kooi wrote:
>> So let's really close that list and discuss things on oe-devel and oe-core
>> ml
>
> I'm on the oe-users mailing list and occasionally help people out, but I have
> to agree with Koen here. It hardly gets any traffic and the nature of OE is that
> every user is a developer or considers themselves so.
If I did it right then mailman will send an autoresponse to each oe-user
mail telling people to use oe-devel and/or oe-core instead.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFN/bhsMkyGM64RGpERAn2YAKCb37RPHS2UZzittqQeoB1UWDVG6QCgrntC
mcC+17LbmSJENtMxwBdQlNE=
=N0fk
-----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID (diff)
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] call for participation on openembedded-users mailing list
Date: Sun, 19 Jun 2011 10:50:52 +0200 [thread overview]
Message-ID: <itkd9c$657$1@dough.gmane.org> (raw)
In-Reply-To: <201106171537.06113.paul.eggleton@linux.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17-06-11 16:37, Paul Eggleton wrote:
> On Friday 17 June 2011 15:28:56 Koen Kooi wrote:
>> So let's really close that list and discuss things on oe-devel and oe-core
>> ml
>
> I'm on the oe-users mailing list and occasionally help people out, but I have
> to agree with Koen here. It hardly gets any traffic and the nature of OE is that
> every user is a developer or considers themselves so.
If I did it right then mailman will send an autoresponse to each oe-user
mail telling people to use oe-devel and/or oe-core instead.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFN/bhsMkyGM64RGpERAn2YAKCb37RPHS2UZzittqQeoB1UWDVG6QCgrntC
mcC+17LbmSJENtMxwBdQlNE=
=N0fk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-06-19 9:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 14:26 call for participation on openembedded-users mailing list Khem Raj
2011-06-17 14:28 ` Koen Kooi
2011-06-17 14:28 ` [OE-core] " Koen Kooi
2011-06-17 14:37 ` Paul Eggleton
2011-06-17 14:37 ` [OE-core] " Paul Eggleton
2011-06-17 15:41 ` Khem Raj
2011-06-17 17:31 ` Philip Balister
2011-06-17 17:41 ` Otavio Salvador
2011-06-19 8:50 ` Koen Kooi [this message]
2011-06-19 8:50 ` [OE-core] " Koen Kooi
2011-06-19 14:08 ` [oe] " Khem Raj
2011-06-19 14:08 ` [OE-core] " Khem Raj
2011-06-19 14:21 ` [oe] " Paul Eggleton
2011-06-19 14:21 ` [OE-core] " Paul Eggleton
2011-06-19 14:27 ` [oe] " Khem Raj
2011-06-19 14:27 ` [OE-core] " Khem Raj
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='itkd9c$657$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.