From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] skeleton reorganization patchset
Date: Thu, 8 Jul 2010 09:38:52 +0200 [thread overview]
Message-ID: <20100708093852.0061dd88@surf> (raw)
In-Reply-To: <AANLkTiluhTWCJ80AeuQrDzlKIGbYrZrMl_yjwZ79C8IH@mail.gmail.com>
On Tue, 6 Jul 2010 18:58:02 +0300
Dmytro Milinevskyy <milinevskyy@gmail.com> wrote:
> Any chance to see this in mainline?
Yes, I don't see any reason why it couldn't be merged. We just need to
wait for Peter to look at this and merge it.
Thanks for your contribution and patience,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-08 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 20:25 [Buildroot] [PATCH 0/2] skeleton reorganization patchset Dmytro Milinevskyy
2010-06-17 21:02 ` Thomas Petazzoni
2010-07-06 15:58 ` Dmytro Milinevskyy
2010-07-08 7:38 ` Thomas Petazzoni [this message]
2010-07-08 14:53 ` Dmytro Milinevskyy
2010-07-18 21:15 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2010-06-10 19:58 Dmytro Milinevskyy
2010-06-15 1:50 ` Dmytro Milinevskyy
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=20100708093852.0061dd88@surf \
--to=thomas.petazzoni@free-electrons.com \
--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 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.