From: Hans-Peter Nilsson <hp@bitrange.com>
To: vladimir.mezentsev@oracle.com
Cc: binutils@sourceware.org
Subject: Re: [PATCH] gprofng: fix regression in build and a rice condition in autoreconf
Date: Fri, 15 Jul 2022 19:25:02 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2207151847310.66434@arjuna.pair.com> (raw)
In-Reply-To: <20220714174142.291910-1-vladimir.mezentsev@oracle.com>
Nit of the day:
On Thu, 14 Jul 2022, Vladimir Mezentsev via Binutils wrote:
> From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
>
> The fix below is for binutils-2_39-branch.
> Usually for gprofng patches, I wait 1 day and apply the patch to the master branch if there were no comments.
>
> What is a procees for binutils-2_39-branch?
> Do I need to wait for direct approval?
>
>
> gprofng/ChangeLog
> 2022-07-14 Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
>
> PR gprofng/29338
> * libcollector/configure.ac (AC_CONFIG_HEADERS): Fix a rice condition.
s/rice/race/.
brgds, H-P
prev parent reply other threads:[~2022-07-15 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 17:41 vladimir.mezentsev
2022-07-15 23:25 ` Hans-Peter Nilsson [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=alpine.BSF.2.20.16.2207151847310.66434@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=binutils@sourceware.org \
--cc=vladimir.mezentsev@oracle.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).