Return-Path:
Delivered-To: apmail-db-derby-commits-archive@www.apache.org
Received: (qmail 27980 invoked from network); 10 Aug 2006 21:22:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur.apache.org with SMTP; 10 Aug 2006 21:22:33 -0000
Received: (qmail 27842 invoked by uid 500); 10 Aug 2006 21:22:32 -0000
Delivered-To: apmail-db-derby-commits-archive@db.apache.org
Received: (qmail 27813 invoked by uid 500); 10 Aug 2006 21:22:32 -0000
Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help:
list-unsubscribe:
List-Post:
Reply-To: "Derby Development"
List-Id:
Delivered-To: mailing list derby-commits@db.apache.org
Received: (qmail 27802 invoked by uid 99); 10 Aug 2006 21:22:32 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Aug 2006 14:22:32 -0700
X-ASF-Spam-Status: No, hits=-9.4 required=10.0
tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [140.211.166.113] (HELO eris.apache.org) (140.211.166.113)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Aug 2006 14:22:31 -0700
Received: by eris.apache.org (Postfix, from userid 65534)
id BDEE41A981A; Thu, 10 Aug 2006 14:22:05 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r430535 - in /db/derby/site/trunk:
build/site/manuals/dita.html
src/documentation/content/xdocs/manuals/dita.xml
Date: Thu, 10 Aug 2006 21:22:05 -0000
To: derby-commits@db.apache.org
From: jta@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20060810212205.BDEE41A981A@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
Author: jta
Date: Thu Aug 10 14:22:04 2006
New Revision: 430535
URL: http://svn.apache.org/viewvc?rev=430535&view=rev
Log:
Updated Derby web site information on creating DITA patches so that
it shows how to create a patch for just one book from the trunk.
Also removed the paragraph about the Apache DB Project using cvs
(the DB docs have since been updated).
Modified:
db/derby/site/trunk/build/site/manuals/dita.html
db/derby/site/trunk/src/documentation/content/xdocs/manuals/dita.xml
Modified: db/derby/site/trunk/build/site/manuals/dita.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/manuals/dita.html?rev=430535&r1=430534&r2=430535&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/manuals/dita.html (original)
+++ db/derby/site/trunk/build/site/manuals/dita.html Thu Aug 10 14:22:04 2006
@@ -328,18 +328,6 @@
-Use 'svn diff' for patches, not 'cvs diff'
-
-
-
-The Apache DB Project recommends using
-cvs diff
-output for creating patches,
-but Derby uses svn,
-so use 'svn diff' instead.
-
-
-
How to create a patch
@@ -396,7 +384,10 @@
-Make the patch. Be sure to create the patch from the trunk/ directory.
+Make the patch.
+Be sure to create the patch from the trunk/ directory.
+The command shown below creates a patch with all the diffs in your
+working copy:
@@ -404,6 +395,16 @@
+
+You can also create a patch with changes for just one book, as shown below:
+
+
+
+
+svn diff src/tuning > xyz.diff
+
+
+
It will be necessary for the community to review your changes, and the best way to do that is to see the HTML output that reflects your changes. Since you have already created HTML output when testing your changes, simply add the relevant HTML files along with the patch file to a zip file.
@@ -475,7 +476,7 @@
-Last Updated: July 18, 2006
+Last Updated: August 10, 2006
-The Apache DB Project recommends using
-cvs diff
-output for creating patches,
-but Derby uses svn,
-so use 'svn diff' instead.
-
-
-
How to create a patch
@@ -204,12 +192,23 @@
-Make the patch. Be sure to create the patch from the trunk/ directory.
+Make the patch.
+Be sure to create the patch from the trunk/ directory.
+The command shown below creates a patch with all the diffs in your
+working copy:
+
+You can also create a patch with changes for just one book, as shown below:
+
+
+
+
It will be necessary for the community to review your changes, and the best way to do that is to see the HTML output that reflects your changes. Since you have already created HTML output when testing your changes, simply add the relevant HTML files along with the patch file to a zip file.