From: Kean Johnston <kean.johnston@gmail.com>
To: overseers@sourceware.org
Subject: Re: Please update SSH key
Date: Thu, 26 Apr 2018 05:57:00 -0000 [thread overview]
Message-ID: <78972ccc-019c-2ee2-140e-ae8ab6439293@gmail.com> (raw)
In-Reply-To: <m31sf4dc4h.fsf@pepe.airs.com>
> Hi Kean, sorry for letting this sit. Glad to hear from you. Your login
> is indeed jkj. I updated the SSH key and e-mail address.
Hello Ian! I have responded privately off-list, but thank you for the
above. As per instruction can you please add me to the binutils project?
Nick Clifton (nickc@redhat.com) has authorised this. I assume I still have
commit-after-approval status on gcc? I am "reviving" the SCO port of GCC
and binutils as it is still heavily in use down here in South Africa and a
number of people have asked me to do this, as the last version of GCC that
worked at all on SCO was 4.2.
Sincere regards,
Kean
next prev parent reply other threads:[~2018-04-26 5:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 18:14 Kean Johnston
2018-04-24 12:26 ` Ian Lance Taylor
2018-04-26 5:57 ` Kean Johnston [this message]
2018-04-26 13:58 ` Frank Ch. Eigler
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=78972ccc-019c-2ee2-140e-ae8ab6439293@gmail.com \
--to=kean.johnston@gmail.com \
--cc=overseers@sourceware.org \
/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).