From: Jason Molenda <jmolenda@apple.com>
To: gdb@sources.redhat.com
Subject: Re: [bangerth@ticam.utexas.edu: GCC review process: how to handle external submissions]
Date: Mon, 10 Mar 2003 00:07:00 -0000 [thread overview]
Message-ID: <128422FC-528C-11D7-A114-003065BC3540@apple.com> (raw)
In-Reply-To: <20030308202134.GB32507@redhat.com>
> From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
> To: gcc@gcc.gnu.org
> Subject: GCC review process: how to handle external submissions
> Date: Sat, 8 Mar 2003 00:40:09 -0600 (CST)
>
>
> I think we have a serious problem here. We are not only losing the
> contributions from these people, we are also scaring them away, and I
> don't think this is wise.
>
> Can we at least discuss the reasons for this, and maybe come up with
> suggestions about how we could improve this process? I think it would
> be
> tremendously helpful if there were someone who
And to further demonstrate that we're all discussing the same problem
at the same time, this came up on the subversion-dev list last week.
Their approach is to have humans do it by hand. cf
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=32389
It's an interesting approach -- it takes advantage of the idea that
there are many volunteers interested in helping a project but aren't
hacker gods. On the other hand, it assumes that the volunteer won't
disappear or let things drop on the floor if he runs short on time...
J
next prev parent reply other threads:[~2003-03-10 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 20:21 Christopher Faylor
2003-03-10 0:07 ` Jason Molenda [this message]
2003-03-10 5:58 ` Christopher Faylor
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=128422FC-528C-11D7-A114-003065BC3540@apple.com \
--to=jmolenda@apple.com \
--cc=gdb@sources.redhat.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