From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 17952f: glibc: Add glibc-2.23
Date: Tue, 23 Feb 2016 18:40:00 -0000 [thread overview]
Message-ID: <56cca7a7dce71_42d03f9b7d74329c1090e4@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 17952f2fa4b37faa27c024f91208751f27395e4c
https://github.com/crosstool-ng/crosstool-ng/commit/17952f2fa4b37faa27c024f91208751f27395e4c
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-02-23 (Tue, 23 Feb 2016)
Changed paths:
M config/libc/glibc.in
Log Message:
-----------
glibc: Add glibc-2.23
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Commit: cb601145999fd269f2acf751360cb6ee74d952b3
https://github.com/crosstool-ng/crosstool-ng/commit/cb601145999fd269f2acf751360cb6ee74d952b3
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-02-23 (Tue, 23 Feb 2016)
Changed paths:
A patches/glibc/2.23/100-Cygwin-doesnt-have-stat64.patch
Log Message:
-----------
glibc: port glibc patch from 2.22 to 2.23
Only one patch ported forward from 2.22:
* 100-Cygwin-doesnt-have-stat64.patch
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Commit: 28aab280f477f8914e1776d57fe84e6ea1e2d98e
https://github.com/crosstool-ng/crosstool-ng/commit/28aab280f477f8914e1776d57fe84e6ea1e2d98e
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-02-23 (Tue, 23 Feb 2016)
Changed paths:
M config/libc/glibc.in
A patches/glibc/2.23/100-Cygwin-doesnt-have-stat64.patch
Log Message:
-----------
Merge pull request #348 from bhundven/update_glibc
Update glibc
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/6df2abc6f177...28aab280f477
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-02-23 18:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56cca7a7dce71_42d03f9b7d74329c1090e4@hookshot-fe2-cp1-prd.iad.github.net.mail \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).