From: M P <buserror@gmail.com>
To: crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: New release of crosstool-ng?
Date: Thu, 01 Dec 2016 10:31:00 -0000 [thread overview]
Message-ID: <CAMMfpEwhqjfK0S-VXv+09toahN5S2vkreFRXZZobKm0BV=Me3Q@mail.gmail.com> (raw)
In-Reply-To: <CAAXf6LVOMX9jSoz-OHFGY0au4PO_2MC3buc5ZRBPrV2Y7v_f4Q@mail.gmail.com>
Another kind reminder...
On 18 October 2016 at 09:37, Thomas De Schampheleire
<patrickdepinguin@gmail.com> wrote:
> On Thu, Oct 6, 2016 at 11:20 AM, Thomas De Schampheleire
> <patrickdepinguin@gmail.com> wrote:
>> Hi Bryan, all,
>>
>> Would it be possible to make a new release of the current code base?
>>
>> I would like to make toolchains using multilib, but want to avoid
>> starting from a crosstool-ng code base that is not released, like a
>> specific git commit.
>>
>> Or perhaps you have some kind of roadmap of changes you want to
>> complete / pull in before making the next release?
>>
>
> Kind reminder...
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2016-12-01 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 9:21 Thomas De Schampheleire
2016-10-18 8:38 ` Thomas De Schampheleire
2016-12-01 10:31 ` M P [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='CAMMfpEwhqjfK0S-VXv+09toahN5S2vkreFRXZZobKm0BV=Me3Q@mail.gmail.com' \
--to=buserror@gmail.com \
--cc=crossgcc@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).