From: Ian Lance Taylor <iant@google.com>
To: Joe Buck <Joe.Buck@synopsys.COM>
Cc: Andrew Pinski <pinskia@gmail.com>,
Diego Novillo <dnovillo@google.com>,
overseers@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Creating gcc-newbies mailing list
Date: Thu, 26 Jul 2007 22:54:00 -0000 [thread overview]
Message-ID: <m31weu7p62.fsf@localhost.localdomain> (raw)
In-Reply-To: <20070726220235.GU15982@synopsys.com>
Joe Buck <Joe.Buck@synopsys.COM> writes:
> I think that when we do steer someone to a different list, we could
> take more care to be polite about it than we sometimes are.
I agree. I also think we should all try harder to avoid flippant or
non-responsive replies to new developers. I think it's important for
the long-term growth of gcc for us to encourage new developers.
The gcc-newbies proposal was Diego's idea, but it was, of course,
based on the kernelnewbies list (see http://kernelnewbies.org/). Is
anybody here able to comment on whether kernelnewbies seems to be
useful or not? Certainly the kernel community is much larger than the
gcc community.
Ian
next prev parent reply other threads:[~2007-07-26 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 20:52 Diego Novillo
2007-07-26 21:05 ` Andrew Pinski
2007-07-26 22:02 ` Joe Buck
2007-07-26 22:54 ` Ian Lance Taylor [this message]
2007-07-28 6:35 ` Jim Blandy
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=m31weu7p62.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=Joe.Buck@synopsys.COM \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
--cc=pinskia@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).