From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Geert Stappers <stappers@stappers.nl>
Cc: Cross GCC <crossgcc@sourceware.org>,
crosstools-ng in debian <721430@bugs.debian.org>,
Geert Stappers <stappers@debian.org>
Subject: Re: crosstool-ng mailinglist and Debian developer
Date: Mon, 05 Jun 2017 23:49:00 -0000 [thread overview]
Message-ID: <7c14c1de7b8a4071abef8a451b0bdc10@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: <20170602175444.GR32244@gpm.stappers.nl>
On 03/06/17 05:54, Geert Stappers wrote:
> On Sun, May 28, 2017 at 09:25:18PM +0000, Chris Packham wrote:
>>
>> I'll incorporate Geert's changes an update PR352. Still looking for an
>> actual Debian developer help get this into unstable/testing/whatever.
>
> (-:
>
> You found that Debian developer: Me
Great. Thanks.
>
> This email is to tell that I found the crossgcc mailing
> and that I'm subscribed to it.
>
> :-)
I've updated https://github.com/crosstool-ng/crosstool-ng/pull/352
Where to next.
next prev parent reply other threads:[~2017-06-05 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170521102020.GL32244@gpm.stappers.nl>
[not found] ` <30127269589a4f4294378118992f41fb@svr-chch-ex1.atlnz.lc>
[not found] ` <20170522201552.GU32244@gpm.stappers.nl>
[not found] ` <20170522210550.GV32244@gpm.stappers.nl>
[not found] ` <ed46b9bf6d4143dabcf8c1f7ed4a870e@svr-chch-ex1.atlnz.lc>
[not found] ` <20170524134245.GU32244@gpm.stappers.nl>
[not found] ` <20170527100256.GB17621@gpm.stappers.nl>
2017-05-28 21:25 ` Regarding: Bug#721430: crosstool-ng, startpoint for further effort Chris Packham
2017-06-02 17:54 ` crosstool-ng mailinglist and Debian developer Geert Stappers
2017-06-05 23:49 ` Chris Packham [this message]
2017-06-06 22:00 ` Geert Stappers
2017-06-08 7:31 Chris Packham
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=7c14c1de7b8a4071abef8a451b0bdc10@svr-chch-ex1.atlnz.lc \
--to=chris.packham@alliedtelesis.co.nz \
--cc=721430@bugs.debian.org \
--cc=crossgcc@sourceware.org \
--cc=stappers@debian.org \
--cc=stappers@stappers.nl \
/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).