This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
PATCH: java/contrib.html
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: gcc-patches at gcc dot gnu dot org
- Cc: java-patches at gcc dot gnu dot org
- Date: Sat, 26 Jul 2003 17:28:13 +0200 (CEST)
- Subject: PATCH: java/contrib.html
This was the last reference to GNATS in our web pages.
Installed.
Gerald
2003-07-26 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* contrib.html: Remove the "Checkins and Gnats" section which
is redundant and partially obsolete.
Index: contrib.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/contrib.html,v
retrieving revision 1.33
diff -u -3 -p -r1.33 contrib.html
--- contrib.html 12 Jul 2003 11:14:10 -0000 1.33
+++ contrib.html 26 Jul 2003 15:25:56 -0000
@@ -92,44 +92,6 @@ projects</a>.</p>
href="../contribute.html">the GCC contribution
instructions</a> for more information.</p>
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
- Checkins and Gnats
- </th>
-</tr>
-</table>
-<br />
-
- <p>If you have direct checkin access for libgcj (meaning write
- permission to the gcc repository as well as permission to commit
- your patch to libgcj), please make sure that your checkins follow
- the standard checkin rules.</p>
-
- <p>First, always make ChangeLog entries. This is not negotiable;
- a checkin without a ChangeLog entry will be reverted. If the
- checkin fixes a bug in Gnats, note this in the entry.</p>
-
- <p>The commit message given to cvs should be the ChangeLog entry.
- If you wrote the entry (your name is at the top), then don't
- include the header. If someone else wrote the entry, do include
- the header. It is customary to make the <tt>cvs commit</tt> log
- message the same as the ChangeLog entry.</p>
-
- <p>If your change fixes a PR, put the text (e.g.)
- ``<tt>Fixes PR java/58</tt>'' into the ChangeLog entry and into the
- cvs commit message. This will cause an automatic message to be
- sent to Gnats to record the commit in the PR.</p>
-
- <p>After checking in a fix which fixes a PR, put the PR into
- ``feedback'' mode. This will send email to the bug's
- originator. In the change message ask them to try the fix and
- report back.</p>
-
- <p>Once the originator reports back, or after some suitable amount
- of time (less time if you are absolutely sure, beyond any shadow
- of a doubt, that the bug has been fixed) close the PR.</p>
-
<br />
<table border="0" cellpadding="4" width="95%">
<tr bgcolor="#b0d0ff">