From: Nick Clifton <nickc@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: binutils@sourceware.org, Vsevolod Alekseyev <sevaa@sprynet.com>
Subject: Re: bad patch - also not on list?
Date: Mon, 20 Nov 2023 16:09:53 +0000 [thread overview]
Message-ID: <60c004c3-2007-4694-8d3d-c32d6d81ecf3@redhat.com> (raw)
In-Reply-To: <875y1wjwqi.fsf@tromey.com>
Hi Tom,
> Nick> I think so. It looks like it might be just one delta that is causing
> Nick> the problem:
> ...
> Nick> If that code is restored, does v9 functionality then return ?
>
> There were several hunks affecting that function, all of them have to be
> fixed. I can do it if you want.
Yes - please do.
Cheers
Nick
prev parent reply other threads:[~2023-11-20 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 6:22 Tom Tromey
2023-11-20 14:32 ` Nick Clifton
2023-11-20 14:55 ` Vsevolod Alekseyev
2023-11-20 15:00 ` Tom Tromey
2023-11-20 16:09 ` 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=60c004c3-2007-4694-8d3d-c32d6d81ecf3@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=sevaa@sprynet.com \
--cc=tom@tromey.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).