You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by ge...@apache.org on 2005/10/01 23:56:41 UTC
svn commit: r293030 - in /incubator/harmony/standard/site:
docs/guidelines.html xdocs/guidelines.xml
Author: geirm
Date: Sat Oct 1 14:56:38 2005
New Revision: 293030
URL: http://svn.apache.org/viewcvs?rev=293030&view=rev
Log:
spelling correction. Thanks tim
Modified:
incubator/harmony/standard/site/docs/guidelines.html
incubator/harmony/standard/site/xdocs/guidelines.xml
Modified: incubator/harmony/standard/site/docs/guidelines.html
URL: http://svn.apache.org/viewcvs/incubator/harmony/standard/site/docs/guidelines.html?rev=293030&r1=293029&r2=293030&view=diff
==============================================================================
--- incubator/harmony/standard/site/docs/guidelines.html (original)
+++ incubator/harmony/standard/site/docs/guidelines.html Sat Oct 1 14:56:38 2005
@@ -473,7 +473,7 @@
to the patch command. When sent to the mailing list, the message
should contain a Subject beginning with <code>[PATCH]</code> and a
distinctive one-line summary corresponding to the action item for that
-patch. Afterwords, the patch summary in the STATUS file should be
+patch. Afterwards, the patch summary in the STATUS file should be
updated to point to the Message-ID of that message.</p>
<p>The patch should be created by using the <CODE>diff -u</CODE>
command from the original software file(s) to the modified software
Modified: incubator/harmony/standard/site/xdocs/guidelines.xml
URL: http://svn.apache.org/viewcvs/incubator/harmony/standard/site/xdocs/guidelines.xml?rev=293030&r1=293029&r2=293030&view=diff
==============================================================================
--- incubator/harmony/standard/site/xdocs/guidelines.xml (original)
+++ incubator/harmony/standard/site/xdocs/guidelines.xml Sat Oct 1 14:56:38 2005
@@ -329,7 +329,7 @@
to the patch command. When sent to the mailing list, the message
should contain a Subject beginning with <code>[PATCH]</code> and a
distinctive one-line summary corresponding to the action item for that
-patch. Afterwords, the patch summary in the STATUS file should be
+patch. Afterwards, the patch summary in the STATUS file should be
updated to point to the Message-ID of that message.</p>
<p>The patch should be created by using the <CODE>diff -u</CODE>