From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] regulus: Adding pxa270 based machine
Date: Tue, 02 Feb 2010 15:50:31 +0100 [thread overview]
Message-ID: <hk9e3m$3t2$1@ger.gmane.org> (raw)
In-Reply-To: <4B682AEC.7000607@balister.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02-02-10 14:38, Philip Balister wrote:
> On 02/02/2010 04:59 AM, Holger Hans Peter Freyther wrote:
>> On Tuesday 02 February 2010 10:38:27 balakrishnan wrote:
>>> Dear OE,
>>> I have mailed four patches to OE dev list on last month
>>> regarding
>>> "pxa270 based machine" inclusion in OE(stable/2009). Can I have status
>>> of my patches?
>>
>> Two things,
>> I think one of the stable/2009 rules is that it needs to be in dev
>> first and
>> will be backported then. So you would have to prepare your changes to
>> .dev and
>> then ask for stable review.
>
> I don't thinnk that is a hard rule,
It still is, about people keep mistakingly interpreting it as "the exact
commit needs to be in .dev". Having fixes in stable/2009 that are not in
.dev is madness, we learned that lesson the hard way with the old ozfam
branches.
> especially since you can now commit
> stuff to dev that will not work in stable.
See above.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLaDu3MkyGM64RGpERApTdAJ9X5VBt5itg/OqX52F9fvZ50lflgACgq1as
4Zl6xCsFp1nl1keXPylUG/c=
=a8Yj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-02 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 9:38 [PATCH] regulus: Adding pxa270 based machine balakrishnan
2010-02-02 9:59 ` Holger Hans Peter Freyther
2010-02-02 13:38 ` Philip Balister
2010-02-02 14:50 ` Koen Kooi [this message]
2010-02-02 22:09 ` Paul Menzel
2010-02-03 8:42 ` Koen Kooi
2010-02-02 13:30 ` Philip Balister
2010-02-02 22:05 ` Paul Menzel
-- strict thread matches above, loose matches on Subject: below --
2010-02-04 5:18 balakrishnan
2010-02-04 7:48 ` Koen Kooi
2010-01-18 12:45 balakrishnan
2010-01-18 9:15 balakrishnan
2010-01-18 9:42 ` Paul Menzel
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='hk9e3m$3t2$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.