From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] commiting patches
Date: Mon, 03 Jan 2011 09:32:50 +0100 [thread overview]
Message-ID: <8762u6crpp.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110103090853.5168f221@surf> (Thomas Petazzoni's message of "Mon, 3 Jan 2011 09:08:53 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Hello,
Thomas> As this is my first message to the list in 2011: happy new year
Thomas> everybody. Best wishes for 2011, and let's have some good BR
Thomas> development during this year :-)
Yeah!
>> I mainly try to handle the patches in fifo mode, but I do also skim
>> new mails. This is both because sometimes updates are sent, and
>> sometimes I see trivial patches that can be handled when I have 5
>> min spare or important bugfixes.
Thomas> I think there is also one criteria that has an impact of the
Thomas> time it takes for a patch to be applied: what the patch
Thomas> does. If the patch is a relatively simple fix to a package, a
Thomas> new package, or something that doesn't have any major impact of
Thomas> Buildroot's infrastructure, or Buildroot usage, then this patch
Thomas> is likely to be handled/merged sooner than something that has
Thomas> broader impact.
Indeed, that's what I meant when I wrote about trivial patches.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-01-03 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 12:30 [Buildroot] commiting patches Heiko Zuerker
2010-12-30 18:18 ` Yann E. MORIN
2010-12-30 20:58 ` Peter Korsgaard
2010-12-30 20:54 ` Peter Korsgaard
2010-12-30 21:04 ` Daniel Nyström
2010-12-30 21:24 ` Sam Ravnborg
2010-12-30 22:07 ` Peter Korsgaard
2010-12-30 22:22 ` Daniel Nyström
2010-12-30 22:25 ` Peter Korsgaard
2010-12-30 22:24 ` Heiko Zuerker
2010-12-30 22:30 ` Peter Korsgaard
2010-12-30 22:39 ` Bryan Hundven
2010-12-30 21:38 ` Heiko Zuerker
2011-01-03 8:08 ` Thomas Petazzoni
2011-01-03 8:32 ` Peter Korsgaard [this message]
2011-01-03 13:47 ` Heiko Zuerker
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=8762u6crpp.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