From: Stefan Hallas Mulvad <shm@hallas.nu>
To: Josh Branning <lovell.joshyyy@gmail.com>
Cc: crossgcc@sourceware.org
Subject: Re: Is crosstool-ng dead?
Date: Sun, 31 Jul 2016 20:35:00 -0000 [thread overview]
Message-ID: <6B8D1029-558D-4C25-8EAE-529E34DCA76A@hallas.nu> (raw)
In-Reply-To: <579BFD98.4040209@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Neither would I, in fact I wish I could contibute & help more than I do - believe it’s a great, interesting and important project.
It’s not clear to me how to effectively contribute, does guidelines exist ? - how is the project managed in terms of development & maintenance.
Best regards,
Stefan
> On Jul 30, 2016, at 3:06 AM, Josh Branning <lovell.joshyyy@gmail.com> wrote:
>
> I for one wouldn't like to see crosstool-ng die.
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
prev parent reply other threads:[~2016-07-31 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 22:35 ANDY KENNEDY
2016-07-25 22:39 ` Bryan Hundven
2016-07-30 1:06 ` Josh Branning
2016-07-30 1:33 ` Bryan Hundven
2016-07-31 20:35 ` Stefan Hallas Mulvad [this message]
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=6B8D1029-558D-4C25-8EAE-529E34DCA76A@hallas.nu \
--to=shm@hallas.nu \
--cc=crossgcc@sourceware.org \
--cc=lovell.joshyyy@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).