public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
	 binutils@sourceware.org,  Vsevolod Alekseyev <sevaa@sprynet.com>
Subject: Re: bad patch - also not on list?
Date: Mon, 20 Nov 2023 08:00:21 -0700	[thread overview]
Message-ID: <875y1wjwqi.fsf@tromey.com> (raw)
In-Reply-To: <6f60fc6b-1bce-4344-a906-d3ed3489aae4@redhat.com> (Nick Clifton's message of "Mon, 20 Nov 2023 14:32:40 +0000")

>>>>> "Nick" == Nick Clifton <nickc@redhat.com> writes:

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.

Tom

  parent reply	other threads:[~2023-11-20 15:00 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 [this message]
2023-11-20 16:09     ` Nick Clifton

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=875y1wjwqi.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=sevaa@sprynet.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).