From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/2017.02.x 1/2] dbus: bump version to 1.10.22
Date: Tue, 15 Aug 2017 21:45:37 +0200 [thread overview]
Message-ID: <20170815214537.52eb3814@windsurf> (raw)
In-Reply-To: <188886FC-9E87-4A0B-B1EE-D7704B4F979C@armadeus.com>
Hello,
On Tue, 15 Aug 2017 21:01:51 +0200, S?bastien Szymanski wrote:
> No particular reason, I just thought it would be easier to backport
> the dbus patch on the version 1.10.22 as it is applied on this
> version on the master branch, rather than backporting it on dbus
> version 1.10.16.
To change things in a LTS branch such as 2017.02.x, we need a much more
solid reason than just "no particular reason".
So I think we need a backport of the dbus patch working around the
expat related issues on top of 1.10.16, instead of bumping dbus to
1.10.22.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-15 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 13:47 [Buildroot] [PATCH/2017.02.x 1/2] dbus: bump version to 1.10.22 Sébastien Szymanski
2017-08-10 13:47 ` [Buildroot] [PATCH/2017.02.x 2/2] dbus: add upstream patch to fix startup hang with with expat >= 2.2.1 Sébastien Szymanski
2017-08-13 12:56 ` Yann E. MORIN
2017-08-14 8:40 ` Sébastien Szymanski
2017-08-14 15:43 ` Yann E. MORIN
2017-08-14 20:44 ` [Buildroot] [PATCH/2017.02.x 1/2] dbus: bump version to 1.10.22 Thomas Petazzoni
2017-08-15 19:01 ` Sébastien Szymanski
2017-08-15 19:45 ` Thomas Petazzoni [this message]
2017-08-21 21:36 ` 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=20170815214537.52eb3814@windsurf \
--to=thomas.petazzoni@free-electrons.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