From: Samuel Thibault <samuel.thibault@gnu.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libc-alpha@sourceware.org, commit-hurd@gnu.org
Subject: Re: [hurd,commited 1/3] hurd: Fix ld.so link
Date: Sun, 01 Dec 2019 20:05:00 -0000 [thread overview]
Message-ID: <20191201200546.jj6b3ha2zjqrotyv@function> (raw)
In-Reply-To: <87mucbdfff.fsf@mid.deneb.enyo.de>
Florian Weimer, le dim. 01 déc. 2019 20:16:52 +0100, a ecrit:
> That may be so, but we cannot change the symbol sets for historic
> releases.
Ah, right, ok, now fixed.
Samuel
next prev parent reply other threads:[~2019-12-01 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 18:53 [hurd,commited 0/3] fixes for hurd port Samuel Thibault
2019-12-01 18:53 ` [hurd,commited 1/3] hurd: Fix ld.so link Samuel Thibault
2019-12-01 18:58 ` Florian Weimer
2019-12-01 19:02 ` Samuel Thibault
2019-12-01 19:16 ` Florian Weimer
2019-12-01 20:05 ` Samuel Thibault [this message]
2019-12-01 18:53 ` [hurd,commited 3/3] hurd: Fix renameat2 error Samuel Thibault
2019-12-01 18:53 ` [hurd,commited 2/3] hurd: make strerror(0) coherent with other ports Samuel Thibault
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=20191201200546.jj6b3ha2zjqrotyv@function \
--to=samuel.thibault@gnu.org \
--cc=commit-hurd@gnu.org \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@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).