From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: 30873@debbugs.gnu.org
Subject: [bug#30873] [PATCH core-updates 1/3] gnu: glibc: Update to 2.27.
Date: Tue, 20 Mar 2018 14:18:05 +0100 [thread overview]
Message-ID: <87r2oe6g36.fsf@gnu.org> (raw)
In-Reply-To: <20180320102419.32286-1-mbakke@fastmail.com> (Marius Bakke's message of "Tue, 20 Mar 2018 11:24:17 +0100")
Hello!
Thanks for working on this update! Crazy that it turned out to be this
difficult.
Marius Bakke <mbakke@fastmail.com> skribis:
> +++ b/gnu/packages/patches/glibc-2.27-git-fixes.patch
> @@ -0,0 +1,12765 @@
> +This patch includes all post-release fixes for version 2.27 up to commit
> +3b922526415d1af93fe5a0e3caf7e6a790cb1619.
> +
> +https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.27/master
> +
> +Generated by "git diff glibc-2.27..release/2.27/master".
In general I’d be in favor of not doing that, unless the fixes are
important (build issue, security issue, etc.), as was the case when we
packaged 2.26; and, if there are important fixes, I’d rather extract
them from the whole patch stream, and skip unrelated changes.
For example, I’m sure we can live without the locale updates that show
up in this patch set. :-)
Do you know which of these patches are really needed?
Thoughts?
Ludo’.
next prev parent reply other threads:[~2018-03-20 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 10:20 [bug#30873] [PATCH core-updates 0/3] glibc 2.27 Marius Bakke
2018-03-20 10:24 ` [bug#30873] [PATCH core-updates 1/3] gnu: glibc: Update to 2.27 Marius Bakke
2018-03-20 10:24 ` [bug#30873] [PATCH core-updates 2/3] gnu: make: Fix compatibility with glibc 2.27 Marius Bakke
2018-03-20 13:19 ` Ludovic Courtès
2018-03-20 10:24 ` [bug#30873] [PATCH core-updates 3/3] gnu: make: End phase on #t Marius Bakke
2018-03-20 13:19 ` Ludovic Courtès
2018-03-20 13:18 ` Ludovic Courtès [this message]
2018-03-20 16:54 ` [bug#30873] [PATCH core-updates 1/3] gnu: glibc: Update to 2.27 Marius Bakke
2018-03-21 18:26 ` Ludovic Courtès
2018-03-22 18:36 ` bug#30873: " Marius Bakke
2018-03-23 9:20 ` [bug#30873] " Ludovic Courtès
2018-03-22 12:53 ` [bug#30873] glibc-2.27 patches Efraim Flashner
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=87r2oe6g36.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30873@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.