From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] kernel-headers: bump 3.{0, 2, 4, 7}.x stable version and add 3.8
Date: Fri, 22 Feb 2013 19:29:41 -0300 [thread overview]
Message-ID: <5127F155.4020301@zacarias.com.ar> (raw)
In-Reply-To: <871uc8dly6.fsf@dell.be.48ers.dk>
On 02/22/2013 07:26 PM, Peter Korsgaard wrote:
> I was going to add this series to -next, but I cannot as it doesn't
> apply (it is made against master).
It can wait for the merge when the release is out.
Less work for you then ;-)
Regards.
prev parent reply other threads:[~2013-02-22 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 15:16 [Buildroot] [PATCH 1/3] kernel-headers: bump 3.{0, 2, 4, 7}.x stable version and add 3.8 Gustavo Zacarias
2013-02-21 15:16 ` [Buildroot] [PATCH 2/3] linux: bump to 3.8.x series Gustavo Zacarias
2013-02-21 15:16 ` [Buildroot] [PATCH 3/3] configs/qemu: bump relevant configs to kernel version 3.8 Gustavo Zacarias
2013-02-22 22:26 ` [Buildroot] [PATCH 1/3] kernel-headers: bump 3.{0, 2, 4, 7}.x stable version and add 3.8 Peter Korsgaard
2013-02-22 22:29 ` Gustavo Zacarias [this message]
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=5127F155.4020301@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox