Author: skitching
Date: Sat Apr 16 20:33:24 2005
New Revision: 161622
URL: http://svn.apache.org/viewcvs?view=rev&rev=161622
Log:
Remove obsolete info about CVS
Modified:
jakarta/commons/proper/commons-build/trunk/xdocs/patches.xml
Modified: jakarta/commons/proper/commons-build/trunk/xdocs/patches.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/xdocs/patches.xml?view=diff&r1=161621&r2=161622
==============================================================================
--- jakarta/commons/proper/commons-build/trunk/xdocs/patches.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/patches.xml Sat Apr 16
20:33:24 2005
@@ -30,7 +30,7 @@
</p>
<p>
Before you start, please find time to browse
- <a href='http://jakarta.apache.org/site/getinvolved.html'>jakarta
contribution guide</a>.
+ <a href='http://jakarta.apache.org/site/getinvolved.html'>the jakarta
contribution guide</a>.
</p>
</section>
<section name="Respect The Original Style">
@@ -85,50 +85,31 @@
</section>
<section name="Creating A Patch">
<p>
- <code>CVS HEAD</code> is the current source. It's stored in
- <a href='http://jakarta.apache.org/site/cvsindex.html'>cvs</a>.
- If you're not familiar with cvs, then
- <a href='http://jakarta.apache.org/site/library.html'>consult these
references</a>
- </p>
- <p>Please create your patch against <code>CVS HEAD</code> since this makes
the job of
- applying the patch much easier. If you don't have a version checked out of
cvs, then check one out.
- If you have, then please do a fresh update before you make your changes.
+ The Jakarta Commons source code repository holds the current source. A link
to information about
+ using the Jakarta Commons source code repository is available on
+ <a href='http://jakarta.apache.org/commons'>the main Jakarta Commons
page</p>. Currently,
+ Jakarta Commons uses the Subversion version control system.
+ </p>
+ <p>Please create your patch against the latest revision of the files in the
source code repository
+ since this makes the job of applying the patch much easier. If you don't
have a version checked
+ out, then check one out. If you have, then please do a fresh update before
you make your changes.
</p>
<p>
- The patch should be in unified format. You can create a patch in this format
(from cvs) by using:
- <source>cvs diff -u <em>File</em> >> <em>patchfile</em></source><br/>
+ The patch should be in unified format. You can create a patch in this format
(from Subversion) by using:
+ <source>svn diff <em>File</em> >> <em>patchfile</em></source><br/>
Try to give your patch files meaningful names. This makes it easier for
developers who need to
apply a number of different patches.
</p>
- <p><strong>Note:</strong><br/>
- If you use <a href='http://www.wincvs.org/'>WinCVS</a>, move to
- <code>[Admin]</code> -> <code>[Command Line]</code> Menu
- and type:
- <source>cvs diff -u</source><br/>
- at <code>[Enter a cvs line command]</code> input field
- (<code>[Commandline Settings] Tab</code>),
- while selecting the target directories or files, in order to create
- unified diffs.
- </p>
- <p>
- In other words, <code>[Alt+A]</code>+<code>[Alt+C]</code>+
- <code>[Alt+C]</code> and type "<code>cvs diff -u</code>".
- </p>
- <p>
- Also, by adding the full path name of WinCVS-Installed directory to
- "path" environment variables, you can use
- "cvs diff" command on the checked-out directory
- (like <code>cvs diff -u > foo.txt</code>) recursively
- via MS-DOS command prompt.
- </p>
</section>
<section name="Submitting A Patch">
<p>
There are two ways to submit a patch:
<ul>
<li>
- By adding the patch as an attachment to a
- <a href='http://jakarta.apache.org/site/bugs.html'>bug report</a>.
+ By adding the patch as an attachment to a bug report. Jakarta Commons
projects
+ use the <a href='http://issues.apache.org/bugzilla'>Apache Bugzilla Bug
Tracker</a>
+ (though other Jakarta and Apache projects may use the
+ <a href='http://issues.apache.org/jira'>Apache Jira Bug Tracker</a>).
</li>
<li>
By mailing the patch as an attachment to the
@@ -145,8 +126,9 @@
<p>If it's a big patch
then adding it to a bug report will save bandwidth on the mailing list (but
remember
to include the url in any follow-up discussions). Using a bug report also
allows you to
- be automatically posted with status updates. Posting to the mailing list
takes you closer to
- the action.
+ be automatically posted with status updates. Note that new bug reports (and
comments on
+ existing ones) automatically get mailed to the commons-dev email list so
there's no
+ need to post a separate email indicating that the patch has been created.
</p>
<p>
If the patch is a fix for a bug that's already been reported then it's best
to add it as an
@@ -154,12 +136,17 @@
developers out there wasting their time by developing independent fixes!
</p>
<p>
- In either case, please give a detailed description of what your patch does
and some reasons
+ If there has already been discussion of the issue on the dev mailing list
(but no bugzilla
+ entry has been created), then posting the patch direct to the mailing list
can be simpler.
+ </p>
+ <p>
+ In any case, please give a detailed description of what your patch does and
some reasons
why it should be committed (if it's not obvious).
</p>
<p>
- All the commons documentation is in cvs - including this document. If you
see anything that's
- wrong or you think that you can add something that's missing then please
submit a patch!
+ All the commons documentation is in the commons version control system -
including this document.
+ If you see anything that's wrong or you think that you can add something
that's missing then
+ please submit a patch!
</p>
<p>
<strong>TIA</strong>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
