Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] outstanding patches in bugzilla
Date: Mon, 16 Feb 2009 14:09:47 +0100	[thread overview]
Message-ID: <87vdracyuc.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1234776032.6303.18.camel@sven> (Sven Neumann's message of "Mon\, 16 Feb 2009 10\:20\:32 +0100")

>>>>> "Sven" == Sven Neumann <s.neumann@phase-zero.de> writes:

 Sven> Hi,

 Sven> just a quick reminder that there are some patches in Bugzilla
 Sven> that were supposed to be committed after the release. Now would
 Sven> be a good time to have another look at them and perhaps get
 Sven> them into trunk. Here's a list of bugs that I consider ready
 Sven> for inclusion, in the order they should preferably be
 Sven> committed:

Don't worry, we haven't forgotten ;)

I looked through some of them last weekend, and except for a few minor
fixups to apply to svn the stuff I saw was fine. I'll verify and
commit stuff shortly.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-02-16 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  9:20 [Buildroot] outstanding patches in bugzilla Sven Neumann
2009-02-16 13:09 ` Peter Korsgaard [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=87vdracyuc.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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