forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: rev 47080 - in forrest/trunk: . src/documentation/content/xdocs
Date Thu, 23 Sep 2004 03:47:39 GMT
Author: crossley
Date: Wed Sep 22 20:47:38 2004
New Revision: 47080

Modified:
   forrest/trunk/build.xml
   forrest/trunk/src/documentation/content/xdocs/mail-lists.xml
Log:
Do not advertise the 'build patch' capability. May need to be removed.
It makes a messy patch when they have other pending changes.


Modified: forrest/trunk/build.xml
==============================================================================
--- forrest/trunk/build.xml	(original)
+++ forrest/trunk/build.xml	Wed Sep 22 20:47:38 2004
@@ -359,8 +359,11 @@
   <!-- =================================================================== -->
   <!-- Use Apache Ant to generate a patch file                             -->
   <!-- =================================================================== -->
-    <target name="patch"
+    <target name="patch">
+<!-- Do not advertise this capability. May need to be removed.
+     It makes a messy patch when they have other pending changes.
         description="Create a patch from your working copy, ready for contribution">
+-->
       <ant antfile="tools/targets/patch.xml" target="patchpackage"/>
     </target>
 

Modified: forrest/trunk/src/documentation/content/xdocs/mail-lists.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/mail-lists.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/mail-lists.xml	Wed Sep 22 20:47:38 2004
@@ -38,10 +38,10 @@
         including the version number of Forrest, your operating system, JDK version, and
         servlet engine, and full details of any errors encountered including
         full error messages and stack traces.</p> 
-          <note>
-      If contributing code patches, use <code>./build.sh patch</code> (or <code>build
patch</code> in Windows)
-      to generate a patch file.   Then use our Jira <link href="site:bugs">issue tracker</link>
to submit it (create
-      a new issue if appropriate).
+      <note>
+      Please use our Jira <link href="site:bugs">issue tracker</link>
+      to submit attachments, rather than the mailing list. Create a new
+      issue, if necessary.
       </note>
     </section> 
 

Mime
View raw message