From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libglib2: Bump to version 2.56.3
Date: Sun, 30 Dec 2018 22:02:40 +0100 [thread overview]
Message-ID: <20181230220240.5aee5473@windsurf> (raw)
In-Reply-To: <20181230203445.GA24639@x230>
Hello Petr,
On Sun, 30 Dec 2018 21:34:46 +0100, Petr Vorel wrote:
> Thanks for info. I've noticed this revert before. Problematic version was 2.58.1
> (updated from 2.56.1). That's why my commit only updated to 2.56.3 (latest
> 2.56.x), which should be ok.
Ah, thanks for spotting that. I didn't notice your bump was just to the
latest 2.56.x. Indeed, it should be much safer. Thanks for pointing it
out, I stupidly thought "it's the big glib bump that is again going to
break everything". I'll apply your patch right away.
Thanks for the reminder and additional explanation.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-30 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 17:38 [Buildroot] [PATCH 1/1] libglib2: Bump to version 2.56.3 Petr Vorel
2018-12-30 19:34 ` Petr Vorel
2018-12-30 20:27 ` Thomas Petazzoni
2018-12-30 20:34 ` Petr Vorel
2018-12-30 21:02 ` Thomas Petazzoni [this message]
2018-12-30 21:46 ` 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=20181230220240.5aee5473@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.