From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Carlos O'Donell <carlos@redhat.com>,
fanquake <fanquake@gmail.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH] doc: correct _FORTIFY_SOURCE doc in features.h
Date: Tue, 31 Jan 2023 17:34:38 -0500 [thread overview]
Message-ID: <1f6dfac9-f159-b109-562c-94453329e722@gotplt.org> (raw)
In-Reply-To: <37d639d7-5f52-92c5-e32f-31a83a308e66@redhat.com>
On 2023-01-31 15:29, Carlos O'Donell wrote:
> On 1/31/23 09:20, Siddhesh Poyarekar wrote:
>> Thanks, that looks correct. Carlos, may I push this before you cut the release?
>>
>> Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
>
> Yes, comment only fix in headers. OK for 2.37. Please push ASAP.
>
Pushed, thanks.
Sid
prev parent reply other threads:[~2023-01-31 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 13:25 fanquake
2023-01-31 14:20 ` Siddhesh Poyarekar
2023-01-31 20:29 ` Carlos O'Donell
2023-01-31 22:34 ` Siddhesh Poyarekar [this message]
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=1f6dfac9-f159-b109-562c-94453329e722@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=fanquake@gmail.com \
--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).