From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] libglib2: bump version to 2.52.2
Date: Sat, 24 Jun 2017 12:11:27 +0200 [thread overview]
Message-ID: <20170624121127.1612ccbc@windsurf.home> (raw)
In-Reply-To: <20170621210103.21058-2-aduskett@codeblue.com>
Hello,
On Wed, 21 Jun 2017 17:01:03 -0400, Adam Duskett wrote:
> Patches were changed to git format, because libglib is a git project.
> 0003-gio-2.0.pc-include-libmount-in-Libs.private.patch was added to upstream
> as of commit:
> https://git.gnome.org/browse/glib/commit/?id=ecdd3c29fc4bd28f01fe53d0528bfee888c9c62c.
>
> Signed-off-by: Adam Duskett <aduskett@codeblue.com>
> ---
> Changes v1 -> v2:
> - Updated commit message to include the url of the commit for patch 003.
> - Added the correct authors to the remaining patches.
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-06-24 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 21:01 [Buildroot] [PATCH 1/1] libglib2: bump version to 2.52.2 Adam Duskett
2017-06-21 21:01 ` [Buildroot] [PATCH v2 " Adam Duskett
2017-06-24 10:11 ` 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=20170624121127.1612ccbc@windsurf.home \
--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