From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] eglibc: bump to version 2.19 SVN R25243
Date: Mon, 7 Apr 2014 15:29:19 +0200 [thread overview]
Message-ID: <20140407152919.2d1147fb@skate> (raw)
In-Reply-To: <1396875879-22199-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 7 Apr 2014 10:04:39 -0300, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> .../2.18-svnr23787/glibc-0001-accept-make4.patch | 33 ----------------------
> package/glibc/glibc.mk | 2 +-
> 2 files changed, 1 insertion(+), 34 deletions(-)
> delete mode 100644 package/glibc/2.18-svnr23787/glibc-0001-accept-make4.patch
So we don't do like glibc where we support both 2.18 and 2.19 ? This is
really a question, maybe it makes sense to only support one version at
a time. In which case we could remove 2.18 from glibc.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-07 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 13:04 [Buildroot] [PATCH] eglibc: bump to version 2.19 SVN R25243 Gustavo Zacarias
2014-04-07 13:29 ` Thomas Petazzoni [this message]
2014-04-07 13:36 ` Gustavo Zacarias
2014-04-07 13:41 ` Thomas Petazzoni
2014-04-08 11:52 ` Gustavo Zacarias
2014-04-08 12:19 ` Peter Korsgaard
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=20140407152919.2d1147fb@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