From: Nick Clifton <nickc@redhat.com>
To: Matthias Klose <doko@debian.org>, binutils@sourceware.org
Subject: Re: 2.41 branch approaching
Date: Thu, 29 Jun 2023 12:44:47 +0100 [thread overview]
Message-ID: <64e5f389-7c93-f831-5f1c-2aca252be601@redhat.com> (raw)
In-Reply-To: <efec7fe9-2f7f-b70d-aea5-ef4411470a2c@debian.org>
Hi Matthias,
> yes, now explicitly filtering out this flag for the tests, patch attached.
That works for me. Patch approved - please apply.
Cheers
Nick
prev parent reply other threads:[~2023-06-29 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:57 Nick Clifton
2023-06-21 18:29 ` Indu Bhagat
2023-06-26 5:34 ` Matthias Klose
2023-06-28 10:58 ` Nick Clifton
2023-06-28 15:21 ` Matthias Klose
2023-06-28 15:59 ` Nick Clifton
2023-06-28 16:27 ` Matthias Klose
2023-06-29 9:34 ` Matthias Klose
2023-06-29 11:44 ` Nick Clifton [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=64e5f389-7c93-f831-5f1c-2aca252be601@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=doko@debian.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).