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, 19 Feb 2018 09:05:04 +0100 [thread overview]
Message-ID: <20180219090504.745c4841@windsurf.lan> (raw)
In-Reply-To: <361202886.84859.1518998584797.JavaMail.zimbra@datacom.ind.br>
Hello,
On Sun, 18 Feb 2018 21:03:04 -0300 (BRT), Carlos Santos wrote:
> > Are you sure 1.7.990 isn't a development version ? Interestingly, their
> > Git repo has no tag with this name:
> > https://cgit.freedesktop.org/ModemManager/ModemManager/refs/tags. It
> > has a 1.8-rc1 version. So it does feel like 1.7.x might be a
> > development version. Could you double check this ?
>
> It is a development version. That's why I submitted an update to the
> latest release version, which is 1.6.12:
>
> https://patchwork.ozlabs.org/patch/871059/
When is the final 1.8.x version expected ? If it's in the very near
future (i.e before 2018.05-rc1), then we could accept the 1.7.x bump for
now, and move to 1.8.x when it lands. Otherwise, I'd prefer to stick
with 1.6.x for now.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-19 8:05 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 [this message]
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
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=20180219090504.745c4841@windsurf.lan \
--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