From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] modem-manager: Update to version 1.7.990
Date: Mon, 2 Apr 2018 00:52:43 +0200 [thread overview]
Message-ID: <20180402005243.00aea819@windsurf> (raw)
In-Reply-To: <2137381520.124019.1519075425250.JavaMail.zimbra@datacom.ind.br>
Hello,
On Mon, 19 Feb 2018 18:23:45 -0300 (BRT), Carlos Santos wrote:
> The announcement message[1], from Sun Jan 21, informs that 1.7.990
> corresponds to 1.8-rc1. From the list of 1.5.99x releases, which spans
> several months, I believe that 1.8 will unlikely be released before
> the end of February.
Then we'll wait for the final 1.8 release to be made before bumping. We
don't typically package release candidate versions in Buildroot.
If people are unhappy with this, I would suggest to work with upstream
so that they adopt a more regular release schedule, so that
modem-manager users can get new features on a more regular basis,
without having to use release candidates.
I've marked the patch as Rejected in patchwork.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-04-01 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 16:38 [Buildroot] [PATCH v2 1/2] libqmi: Update to use libqmi 1.20.0 Jared Bents
2018-02-16 16:38 ` [Buildroot] [PATCH v2 2/2] modem-manager: Update to version 1.7.990 Jared Bents
2018-02-16 20:53 ` Thomas Petazzoni
2018-02-19 0:03 ` Carlos Santos
2018-02-19 8:05 ` Thomas Petazzoni
2018-02-19 21:23 ` Carlos Santos
2018-02-20 14:57 ` Julien Boibessot
2018-02-20 15:56 ` Carlos Santos
2018-02-23 11:17 ` Aleksander Morgado
2018-04-01 22:52 ` 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=20180402005243.00aea819@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