From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [2011.03-maintenance] Pull request for new TI machines, angstrom and qt4 fixes
Date: Thu, 31 Mar 2011 13:04:47 +0200 [thread overview]
Message-ID: <in1n4g$hvs$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTikn4r-ScRstfT_r-Adw36=682MEb_XHMKn+qs3_@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 31-03-11 12:51, Frans Meulenbroeks wrote:
> Adding new machines on a maintenance branch seems somewhat odd as new
> somewhat conflicts with maintenance.
> is this what we want? And if so, what about adding new recipes?
Since you aren't using, developing or supporting 2011.03-maintenance, I
strongly object to your usage of 'we'.
Furthermore, this isn't the first time that new machines would get added
to 2011.03-maintenance.
People really should read
http://wiki.openembedded.org/index.php/2011.03-maintenance
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNlF/PMkyGM64RGpERAh/tAKCwDlaBHSrMDziiP1j/lHAga2zyqQCfT+Ke
FRylHre7/eQRdNlkDw3Xe94=
=6IbX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-31 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 7:45 [2011.03-maintenance] Pull request for new TI machines, angstrom and qt4 fixes Denys Dmytriyenko
2011-03-31 9:10 ` Koen Kooi
2011-03-31 10:51 ` Frans Meulenbroeks
2011-03-31 11:04 ` Koen Kooi [this message]
2011-03-31 11:57 ` Frans Meulenbroeks
2011-03-31 12:36 ` Philip Balister
2011-03-31 16:47 ` Tom Rini
2011-03-31 20:28 ` Frans Meulenbroeks
2011-03-31 16:44 ` Tom Rini
2011-03-31 17:40 ` Denys Dmytriyenko
-- strict thread matches above, loose matches on Subject: below --
2011-03-31 18:07 Denys Dmytriyenko
2011-03-31 20:36 ` Tom Rini
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='in1n4g$hvs$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.