From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH] gethostid (Linux variant): Switch to struct scratch_buffer [BZ #18023]
Date: Tue, 18 Sep 2018 12:09:00 -0000 [thread overview]
Message-ID: <mvmworjvwfu.fsf@suse.de> (raw)
In-Reply-To: <87worjvzpc.fsf@mid.deneb.enyo.de> (Florian Weimer's message of "Tue, 18 Sep 2018 12:59:11 +0200")
On Sep 18 2018, Florian Weimer <fw@deneb.enyo.de> wrote:
> Oops. Do you want me to write a patch?
There is one attached to the bug.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-09-18 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 15:46 Florian Weimer
2018-06-26 16:58 ` Adhemerval Zanella
2018-06-26 17:33 ` Florian Weimer
2018-06-26 17:52 ` Adhemerval Zanella
2018-09-18 10:51 ` Andreas Schwab
2018-09-18 10:59 ` Florian Weimer
2018-09-18 12:09 ` Andreas Schwab [this message]
2018-09-18 12:32 ` Florian Weimer
2018-06-26 18:16 ` DJ Delorie
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=mvmworjvwfu.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.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).