public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Michael Witten <mfwitten@MIT.EDU>
Cc: gcc-help@gcc.gnu.org
Subject: Re: [Progress] Tiny GCC: Pure, Unadulterated, Object Code
Date: Mon, 28 Jan 2008 00:46:00 -0000	[thread overview]
Message-ID: <479B5CFF.50806@redhat.com> (raw)
In-Reply-To: <2A9296A3-2EBE-436A-B119-2D068B4F4B28@mit.edu>

Michael Witten wrote:
> 
> On 25 Jan 2008, at 6:11 PM, Michael Witten wrote:
> 
>> That kind of documentation could go a long way in encouraging new
>> developers to get involved, because it would allow them to avoid
>> a first impression wrought with frustration.
> 
> I just stumbled across this website, which looks quite inviting:
> http://kernelnewbies.org
> 
> Something as abstruse and magical as gcc could benefit from
> a similar initiative.

What's to stop people who want to do this from writing to the gcc
Wiki instead?  http://gcc.gnu.org/wiki/HomePage

Andrew.

  reply	other threads:[~2008-01-26 16:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 12:21 Michael Witten
2008-01-24 14:29 ` Ian Lance Taylor
2008-01-25  4:23 ` Brian Dessent
2008-01-26  2:47   ` Michael Witten
2008-01-26 16:17     ` [Progress] " Michael Witten
2008-01-26 22:16       ` Michael Witten
2008-01-28  0:46         ` Andrew Haley [this message]
2008-01-27 13:07       ` Michael Witten
2008-01-27  8:45     ` Brian Dessent
2008-01-29  1:36       ` Scott Moore
2008-01-29 15:55       ` Michael Witten
2008-01-29 16:56         ` Brian Dessent
2008-01-29 18:16           ` Michael Witten
2008-01-29 18:36             ` Brian Dessent
2008-01-29 20:31               ` Michael Witten
2008-01-30  1:14             ` NightStrike
2008-01-30  7:09               ` Michael Witten
2008-01-30 10:20             ` Ian Lance Taylor
2008-01-30 10:54               ` Michael Witten
2008-01-30 12:09                 ` Ian Lance Taylor
2008-01-29 14:22 ` John Carter
2008-01-29 15:40   ` Michael Witten

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=479B5CFF.50806@redhat.com \
    --to=aph@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=mfwitten@MIT.EDU \
    /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).