From: Richard Guenther <richard.guenther@gmail.com>
To: Iain Buclaw <ibuclaw@ubuntu.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Merging gdc (GNU D Compiler) into gcc
Date: Thu, 10 May 2012 09:48:00 -0000 [thread overview]
Message-ID: <CAFiYyc0ZP2AADBqpd8eT45Un+cOGNY5m7+ZWzx_rjSOYFAdNEg@mail.gmail.com> (raw)
In-Reply-To: <CABOHX+dEHtySwgdqoxDEFS=VAL0S-3DArRTdeUA26xEEV2r3tg@mail.gmail.com>
On Thu, May 10, 2012 at 11:37 AM, Iain Buclaw <ibuclaw@ubuntu.com> wrote:
> On 11 April 2012 15:12, Iain Buclaw <ibuclaw@ubuntu.com> wrote:
>> On 4 October 2011 08:08, Iain Buclaw <ibuclaw@ubuntu.com> wrote:
>>> Hi,
>>>
>>> I've have received news from Walter Bright that the license of the D
>>> frontend has been assigned to the FSF. As the current maintainer of
>>> GDC, I would like to get this moved forward, starting with getting the
>>> ball rolling. What would need to be done? And what are the processes
>>> required? (ie: passing the project through to technical review.)
>>>
>>> The current home of GDC is here: https://bitbucket.org/goshawk/gdc
>>>
>>
>>
>> This has been rather long wait from my side of the pond (moving has
>> taken away quite some time from my side). But I'll be in a position
>> to begin discussion on arrangements this weekend for patches to be
>> submitted for GCC 4.8.
>>
>> I would be grateful if we could start and maintain discussions on
>> making this happen, and I hope some sort of agreement could be reached
>> by the end of the month.
>>
>
> I would like to give a gentle reminder of this. Where should I be
> posting the proposed patches to? The frontend and runtime library
> alone would be a few megabytes in size.
Patches should be posted to gcc-patches@gcc.gnu.org - for large
drop-ins (sub-)tarballs are prefered. I suppose one way would be
to merge GDC to a branch in the GCC SVN repository first. Note
that gcc-patches has a size limit (not sure how large it was though),
hosting files somewhere and providing links would be another
way of providing them.
Richard.
>
> Regards
>
> --
> Iain Buclaw
>
> *(p < e ? p++ : p) = (c & 0x0f) + '0';
next prev parent reply other threads:[~2012-05-10 9:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 7:08 Iain Buclaw
2011-10-04 8:41 ` Andrew Haley
2011-10-04 18:19 ` Iain Buclaw
2011-10-06 15:15 ` Iain Buclaw
2011-10-04 14:03 ` Ian Lance Taylor
2011-10-04 19:30 ` Iain Buclaw
2011-10-04 19:37 ` Andrew Pinski
2011-10-04 20:13 ` Iain Buclaw
2011-10-04 23:11 ` Ian Lance Taylor
2011-10-04 21:41 ` David Brown
2011-10-04 21:47 ` David Brown
2011-10-04 22:51 ` Andrew Pinski
2011-10-05 9:31 ` David Brown
2011-10-05 10:00 ` David Brown
2011-10-05 12:49 ` Andi Kleen
2011-10-05 14:44 ` David Brown
2011-10-05 14:59 ` David Brown
2011-10-04 20:41 ` Tom Tromey
2011-10-05 0:59 ` Ian Lance Taylor
2011-10-05 4:14 ` Iain Buclaw
2011-10-11 14:05 ` Dave Korn
2011-10-04 16:50 ` Joseph S. Myers
2011-10-04 19:45 ` Iain Buclaw
2011-10-04 19:56 ` Joseph S. Myers
2011-10-06 8:31 ` Walter Bright
2012-04-11 14:12 ` Iain Buclaw
2012-04-13 23:01 ` Dave Korn
2012-05-10 9:37 ` Iain Buclaw
2012-05-10 9:48 ` Richard Guenther [this message]
2012-05-10 9:53 ` Iain Buclaw
2012-05-10 11:51 ` Manuel López-Ibáñez
2012-07-21 20:00 ` Florian Weimer
2012-07-24 20:37 ` Iain Buclaw
-- strict thread matches above, loose matches on Subject: below --
2010-11-08 23:13 Merging gdc (Gnu " Walter Bright
2010-11-09 1:14 ` Joseph S. Myers
2010-11-09 7:22 ` Walter Bright
2010-11-09 13:09 ` Andrew Haley
2010-11-09 13:57 ` Jakub Jelinek
2010-11-09 16:43 ` Joe Buck
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=CAFiYyc0ZP2AADBqpd8eT45Un+cOGNY5m7+ZWzx_rjSOYFAdNEg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=ibuclaw@ubuntu.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).