From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Patch submission
Date: Fri, 05 Feb 2010 12:29:08 +0100 [thread overview]
Message-ID: <87636bq5tn.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4B6BFCCB.7000506@carallon.com> (Will Wagner's message of "Fri, 05 Feb 2010 11:11:07 +0000")
>>>>> "Will" == Will Wagner <will_wagner@carallon.com> writes:
Will> I have submitted a number of patches recently, some of which have been
Will> committed.
Will> My question, mainly to Peter I guess, is what do i have to do to get
Will> my other patches included? I realise they are slightly larger changes
Will> and would need some testing. Should I log them in bugzilla so they
Will> don't get lost?
Yes, please do. Real life has been getting in the way of serious BR
development lately, sorry about that.
We are getting overdue for a 2010.02-rc1 release, which I'll make after
FOSDEM (E.G. Monday/Tuesday). This means that no new features will get
added until after the 2010.02 release, so having those patches in
bugzilla will ensure that they aren't forgotten.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-02-05 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 11:11 [Buildroot] Patch submission Will Wagner
2010-02-05 11:29 ` 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=87636bq5tn.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