From: Koen Martens <gmc@sonologic.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] capnproto: new package
Date: Sat, 22 Jul 2017 21:25:29 +0200 [thread overview]
Message-ID: <20170722192528.GA4860@sunra> (raw)
In-Reply-To: <20170722100041.GA9929@scaer>
On Sat, Jul 22, 2017 at 12:00:41PM +0200, Yann E. MORIN wrote:
> Koen, All,
>
> On 2017-07-22 08:16 +0200, Koen Martens spake thusly:
> > Not going to be accepted i guess. No problem, we'll maintain it in our
> > private branch then. Would've been nice to have had a short note
> > though that it isn't going to be merged.
>
> That's not that it won't be accepted, it's just that we have a *lot* of
> pending patches, and we can't handle everything on a whim:
> https://patchwork.ozlabs.org/project/buildroot/list/
>
> At the time of writing, that's 237 pending patches...
Ouch, ok, I wasn't aware of that. I guess that's good news though, lots
of contributions :)
Thanks for taking the time to review the second version of the patch,
i'll have a look at fixing it.
Thanks,
Koen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170722/9794a2d9/attachment.asc>
prev parent reply other threads:[~2017-07-22 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 16:21 [Buildroot] [PATCH v2] capnproto: new package Koen Martens
2017-07-17 18:59 ` Koen Martens
2017-07-22 6:16 ` Koen Martens
2017-07-22 10:00 ` Yann E. MORIN
2017-07-22 19:25 ` Koen Martens [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=20170722192528.GA4860@sunra \
--to=gmc@sonologic.nl \
--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