From: Nick Clifton <nickc@redhat.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Neeraj Singh <nksingh85@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [BUG Report] objdump on mingw64 does not display debug_rnglists properly
Date: Tue, 30 Nov 2021 17:39:59 +0000 [thread overview]
Message-ID: <e60ee42c-3060-0dc2-cbdd-9c855520433a@redhat.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2111301435020.63@tvgsbejvaqbjf.bet>
Hi Johannes,
> I believe that the binutils team prefers bug reports via
> https://sourceware.org/bugzilla/, as per
> https://www.gnu.org/software/binutils/.
We do - and I really should have said this myself. Thanks for reminding us.
> Would you mind opening a ticket there?
As it happens I have already checked in a patch to fix the problem, but Neeraj
does file a ticket I will update it with a link to the commit.
Cheers
Nick
next prev parent reply other threads:[~2021-11-30 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 23:34 Neeraj Singh
2021-11-30 13:21 ` Nick Clifton
2021-11-30 13:36 ` Johannes Schindelin
2021-11-30 17:39 ` Nick Clifton [this message]
2021-11-30 19:21 ` Neeraj Singh
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=e60ee42c-3060-0dc2-cbdd-9c855520433a@redhat.com \
--to=nickc@redhat.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=binutils@sourceware.org \
--cc=nksingh85@gmail.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).