From: Stephen Casner <casner@acm.org>
To: Nick Clifton <nickc@redhat.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Would you like to be the PDP11 maintainer for the binutils ?
Date: Tue, 21 Apr 2020 17:44:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.OSX.2.21.9999.2004211632550.79966@auge.attlocal.net> (raw)
In-Reply-To: <190e899a-0542-e65a-9496-a59c88cf6336@redhat.com>
Nick,
> Would you be interested in becoming the PDP11 maintainer for the binutils ?
> It would mean that you can self-approve patches that are PDP11 specific.
I could do that. I am retired so that means I don't need approval
from anyone, but it also means I don't have any company resources to
draw upon.
> Plus it would mean that we would now have someone who cares about the PDP11
> architecture and is interested in making sure that it works and continues
> to work in the future.
So, for example, if someone introduces a new test that fails for the
PDP11 when you do your survey, you'd bring it to my attention?
> If so then you will need write access to the repository (you may have this
> already - I loose track of these kind of things), and then to make it
> official, please add your name and email to the binutils/MAINTAINERS file.
> The location in the file should be obvious.
I don't have write access, but I will submit a request with your email
as the approver.
In gcc/MAINTAINERS I see a long list of specific ports and individuals
who are maintainers for those ports, but in binutils/MAINTAINERS I did
not see specific ports or individuals listed.
At the instigation of Paul Koning, PDP11 maintainter for gcc, I have
implemented a first crack at pdp11-elf32 so that we might get C++ to
work on the PDP11 (I'm stuck on trying to build up the libraries at
this point). I also mentioned to you the changes I would like to make
to nm to show addresses as 4 digits for 16-bit targets and to adjust
the spacing according to the selected radix. What is the convention
to present such changes for review? Should a PR be filed for each, or
just propose the change with a patch on binutils@sourceware.org?
-- Steve
next prev parent reply other threads:[~2020-04-22 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 21:35 PATCH: PR25830: Exclude gdb & gprof for pdp11 Stephen Casner
2020-04-20 13:57 ` Simon Marchi
2020-04-21 10:26 ` Would you like to be the PDP11 maintainer for the binutils ? Nick Clifton
2020-04-22 0:44 ` Stephen Casner [this message]
2020-04-22 3:43 ` Alan Modra
2020-04-22 5:01 ` Stephen Casner
2020-04-22 12:21 ` Nick Clifton
2020-04-25 23:43 ` Stephen Casner
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=alpine.OSX.2.21.9999.2004211632550.79966@auge.attlocal.net \
--to=casner@acm.org \
--cc=binutils@sourceware.org \
--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).