This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Shorten patch ping timeout
On Fri, Jun 20, 2003 at 02:31:15AM +0200, Gerald Pfeifer wrote:
> On Thu, 19 Jun 2003, Matt Kraai wrote:
> > Accepted pratice appears to be that unreviewed patches should be
> > pinged after a week. The following patch documents this.
>
> One month certainly is way too long, one week is probably the lower
> bound acceptable. I'd say, let's lower the description to two weeks
> or ten days, for now.
>
> Would you mind adding a short note that these reminders should include
> a short description of what the patch is about?
>
> Those
>
> Ping.
>
> http://gcc.gnu.org/ml/....
>
> messages really aren't too useful, compared to those featuring a one-line
> description of the patch.
Is the following OK then?
--
Matt Kraai kraai@alumni.cmu.edu Debian GNU/Linux
Index: htdocs/contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.50
diff -3 -c -p -r1.50 contribute.html
*** htdocs/contribute.html 2 Jun 2003 10:49:50 -0000 1.50
--- htdocs/contribute.html 20 Jun 2003 00:36:08 -0000
*************** the <a href="cvs.html">Anonymous read-on
*** 219,230 ****
href="cvswrite.html">Read-write CVS access</a> pages.</p>
<p>If you do not receive a response to a patch that you have submitted
! within a month or so, it may be a good idea to chase it by sending a
follow-up email to <a
href="mailto:gcc-patches@gcc.gnu.org";>gcc-patches@gcc.gnu.org</a>.
Patches can occasionally fall through the cracks. Please be sure to
! include the URL of the entry in the mailing list archive of the
! original submission.</p>
<p>Patches to the standard C++ library (libstdc++-v3), and its web
pages, and discussion of such patches, should go to <a
--- 219,230 ----
href="cvswrite.html">Read-write CVS access</a> pages.</p>
<p>If you do not receive a response to a patch that you have submitted
! within two weeks or so, it may be a good idea to chase it by sending a
follow-up email to <a
href="mailto:gcc-patches@gcc.gnu.org";>gcc-patches@gcc.gnu.org</a>.
Patches can occasionally fall through the cracks. Please be sure to
! include a brief summary of the patch and the URL of the entry in the
! mailing list archive of the original submission.</p>
<p>Patches to the standard C++ library (libstdc++-v3), and its web
pages, and discussion of such patches, should go to <a