From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 01/10] libglib2: Bump libglib2 to 2.36.1
Date: Wed, 22 May 2013 08:55:52 +0200 [thread overview]
Message-ID: <20130522085552.7079aae2@skate> (raw)
In-Reply-To: <1369177864-6236-2-git-send-email-spenser@gillilanding.com>
Dear Spenser Gilliland,
On Tue, 21 May 2013 18:10:55 -0500, Spenser Gilliland wrote:
> This patch bumps libglib2 to version 2.36.1. In addition this bumps glibmm and glib-networking to 2.36.1.
Please wrap your commit logs to ~80 characters.
Is there any reason for bumping libglib2, glibmm and glib-networking in
the same patch? I seem to recall in earlier versions of your patch
series, you had separate patches for those bumps.
There are two cases here:
*) Either the version bump are needed all together, because there is
some tight version dependency between glibmm, glib-networking and
libglib2. (I.e, if for example, bumping libglib2, but not bumping
glibmm would break the build of the old version of glibmm on top of
the new version of libglib2).
*) Or the version bumps are independent, or dependent only on lower
packages being bumped. In this case, we generally prefer to have
separate patches. So in this case, I guess bump libglib2 first, and
then either glibmm or glib-networking in whichever order your
prefer.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-22 6:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 23:10 [Buildroot] [PATCH v7 00/10] add Gstreamer 1.X for gst-omx support Spenser Gilliland
2013-05-21 23:10 ` [Buildroot] [PATCH v7 01/10] libglib2: Bump libglib2 to 2.36.1 Spenser Gilliland
2013-05-22 6:55 ` Thomas Petazzoni [this message]
2013-05-22 15:57 ` Spenser Gilliland
2013-05-22 17:30 ` Yann E. MORIN
2013-05-22 18:01 ` Thomas Petazzoni
2013-05-26 9:26 ` Thomas Petazzoni
2013-05-21 23:10 ` [Buildroot] [PATCH v7 02/10] gstreamer1: Add gstreamer version 1.0.7 package Spenser Gilliland
2013-05-21 23:10 ` [Buildroot] [PATCH v7 03/10] gst1-plugins-base: add gstreamer1 base plugins Spenser Gilliland
2013-05-21 23:10 ` [Buildroot] [PATCH v7 04/10] gst1-plugins-good: add gstreamer1 good plugins Spenser Gilliland
2013-05-21 23:10 ` [Buildroot] [PATCH v7 05/10] gst1-plugins-bad: add gstreamer1 bad plugins Spenser Gilliland
2013-05-21 23:11 ` [Buildroot] [PATCH v7 06/10] gst1-plugins-ugly: add gstreamer1 ugly plugins Spenser Gilliland
2013-05-21 23:11 ` [Buildroot] [PATCH v7 07/10] libvpx: new package libvpx Spenser Gilliland
2013-05-21 23:11 ` [Buildroot] [PATCH v7 08/10] gst1-plugins-good: add libvpx support Spenser Gilliland
2013-05-21 23:11 ` [Buildroot] [PATCH v7 09/10] libopenmax: Add libopenmax virtual package Spenser Gilliland
2013-05-21 23:11 ` [Buildroot] [PATCH v7 10/10] gst-omx: add gst-omx package Spenser Gilliland
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=20130522085552.7079aae2@skate \
--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