From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"H.J. Lu" <hjl.tools@gmail.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Mike Fabian <mfabian@redhat.com>,
Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: glibc 2.28 update contrib.texi.
Date: Fri, 27 Jul 2018 23:16:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.21.1807280016100.27000@eddie.linux-mips.org> (raw)
In-Reply-To: <b4e1ee2b-879c-e5c9-6c34-e6aae5e0a091@redhat.com>
On Fri, 27 Jul 2018, Carlos O'Donell wrote:
> Maciej,
>
> OK with this update?
Fine with me, thanks!
Maciej
next prev parent reply other threads:[~2018-07-27 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 20:10 Carlos O'Donell
2018-07-27 20:22 ` H.J. Lu
2018-07-27 21:32 ` Adhemerval Zanella
2018-07-27 23:16 ` Maciej W. Rozycki [this message]
2018-07-28 1:18 ` Tulio Magno Quites Machado Filho
2018-07-28 1:21 ` Carlos O'Donell
2018-07-28 1:23 ` Carlos O'Donell
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=alpine.LFD.2.21.1807280016100.27000@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mfabian@redhat.com \
--cc=tuliom@linux.vnet.ibm.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.
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).