From: Sven Neumann <s.neumann@phase-zero.de>
To: buildroot@busybox.net
Subject: [Buildroot] preferred procedure to get new packages included
Date: Thu, 15 Jan 2009 15:07:59 +0100 [thread overview]
Message-ID: <1232028479.6759.2.camel@sven> (raw)
In-Reply-To: <87zlhuazqj.fsf@macbook.be.48ers.dk>
Hi,
On Wed, 2009-01-14 at 12:33 +0100, Peter Korsgaard wrote:
> I've seen your patch, but haven't had time for a closer review yet.
> We're trying to stabilize the tree and get a release out by February,
> so it won't get committed until then.
That's of course sad as it would like to see these packages included in
that release if possible. I have now attached an updated patch with some
cleanups and fixes to the bug report. Perhaps it is useful for anyone.
https://bugs.busybox.net/show_bug.cgi?id=35
Sven
next prev parent reply other threads:[~2009-01-15 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 11:20 [Buildroot] preferred procedure to get new packages included Sven Neumann
2009-01-14 11:33 ` Peter Korsgaard
2009-01-15 14:07 ` Sven Neumann [this message]
2009-01-15 14:14 ` Peter Korsgaard
2009-01-15 21:08 ` Ulf Samuelsson
2009-01-16 9:37 ` Sven Neumann
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=1232028479.6759.2.camel@sven \
--to=s.neumann@phase-zero.de \
--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