From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libjwt: new package.
Date: Tue, 21 Aug 2018 22:25:35 +0200 [thread overview]
Message-ID: <20180821222535.321cb4af@windsurf> (raw)
In-Reply-To: <CAMKz0YoE0s8nNMoxy2-iHLeBKPkNOt7rGBq3gg4B8mxt_QQ5SA@mail.gmail.com>
Hello,
On Tue, 21 Aug 2018 22:20:32 +0200, Mikael Eliasson wrote:
> > Don;t worry, it is not lost, but:
> >
> > 1. There are currently 197 patches pending:
> > https://patchwork.ozlabs.org/project/buildroot/list/
> >
> > 2. We are in feature-freeze for the release scheduled by the end of the
> > month.
> >
> > 3. The Github repository is not the official tree; it is only a mirror.
> > The official tree is: https://git.buildroot.org/buildroot/
>
> OK. Just wanted to know if it was worth putting in the effort on the next
> patch I'm working on.
Yes, it is definitely worth the effort. The latency to get patches
merged can be pretty high, but no patches gets forgotten, thanks to our
patch tracking system.
New packages are rarely controversial (unless they have some
significant complexity or strange things) and are very likely to be
merged. But it does take some time.
Thanks for your contributions!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-21 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 20:29 [Buildroot] [PATCH 1/1] libjwt: new package Mikael
2018-08-12 12:39 ` Thomas Petazzoni
2018-08-12 16:08 ` Mikael Eliasson
2018-08-12 19:25 ` Yann E. MORIN
2018-08-21 18:34 ` Mikael Eliasson
2018-08-21 19:54 ` Yann E. MORIN
2018-08-21 20:20 ` Mikael Eliasson
2018-08-21 20:25 ` Thomas Petazzoni [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=20180821222535.321cb4af@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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