From: John Ericson <git@JohnEricson.me>
To: binutils@sourceware.org
Cc: "Nick Clifton" <nickc@redhat.com>, "Alyssa Ross" <hi@alyssa.is>
Subject: [PATCH v2] Make *-netbsd mean ELF rather than a.out for all CPU
Date: Tue, 3 Aug 2021 14:59:16 -0400 [thread overview]
Message-ID: <20210803185917.929706-1-git@JohnEricson.me> (raw)
In-Reply-To: <b71cdfb9-9eba-441a-93ef-f36d840412ef@www.fastmail.com>
> A patch with the typo corrected and NS32K added to the obsolete list
> in config.bfd is approved, provided that you can confirm that the
> NS32K is no longer supported.
Sorry to be slow to get back to you, Nick. I believe I've done both of
those things, and also tested it a few ways.
next prev parent reply other threads:[~2021-08-03 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 23:01 Making *-netbsd-* to mean ELF not a.out for all CPUs John Ericson
2021-06-14 11:18 ` Nick Clifton
2021-06-18 1:59 ` John Ericson
2021-06-18 2:36 ` [PATCH] Remove `netbsdpe` support John Ericson
2021-06-29 15:48 ` Nick Clifton
2021-06-29 15:58 ` John Ericson
2021-07-18 22:32 ` [PATCH v2] " John Ericson
2021-07-21 1:38 ` Alan Modra
2021-07-06 19:55 ` [PATCH] Make *-netbsd mean ELF rather than a.out for all CPU archs John Ericson
2021-07-16 15:54 ` Nick Clifton
2021-07-18 22:00 ` John Ericson
2021-08-03 18:59 ` John Ericson [this message]
2021-08-03 18:59 ` [PATCH v2] Make *-netbsd mean ELF rather than a.out for all CPU archs, deprecate ns32k-netbsd John Ericson
2021-08-11 12:19 ` Nick Clifton
2021-09-03 20:11 ` Jan-Benedict Glaw
2021-09-10 14:52 ` GAS broken for m68k-netbsdelf (was: [PATCH v2] Make *-netbsd mean ELF rather than a.out for all CPU archs, deprecate ns32k-netbsd) Jan-Benedict Glaw
2021-09-13 7:34 ` Alan Modra
2021-07-20 17:14 ` Making *-netbsd-* to mean ELF not a.out for all CPUs Maciej W. Rozycki
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=20210803185917.929706-1-git@JohnEricson.me \
--to=git@johnericson.me \
--cc=binutils@sourceware.org \
--cc=hi@alyssa.is \
--cc=nickc@redhat.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).