You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by da...@apache.org on 2013/06/14 10:17:56 UTC
svn commit: r1492992 -
/subversion/site/publish/docs/community-guide/general.part.html
Author: danielsh
Date: Fri Jun 14 08:17:56 2013
New Revision: 1492992
URL: http://svn.apache.org/r1492992
Log:
* docs/community-guide/general.part.html
(patches): Move existing content to..
(patches-submission) .. this subsection, and ..
(patches-writing) .. add this new subsection.
Modified:
subversion/site/publish/docs/community-guide/general.part.html
Modified: subversion/site/publish/docs/community-guide/general.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/general.part.html?rev=1492992&r1=1492991&r2=1492992&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/general.part.html (original)
+++ subversion/site/publish/docs/community-guide/general.part.html Fri Jun 14 08:17:56 2013
@@ -655,6 +655,35 @@ manual</a> for a complete list of comman
title="Link to this section">¶</a>
</h2>
+<div class="h3" id="patches-writing">
+<h3>Writing patches
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#patches-writing"
+ title="Link to this section">¶</a>
+</h3>
+
+<p>To get the latest source code, run:</p>
+<pre>svn checkout https://svn.apache.org/repos/asf/subversion/trunk/ svn-trunk</pre>
+<p>and follow the instructions in the <tt>INSTALL</tt> file. (If you do not
+have an <tt>svn</tt> binary, <a href="/download/">download a source
+tarball</a>.)</p>
+
+<p>If your patch implements a new feature, or changes large amounts of code,
+please remember to discuss it on the dev@ list first. (IRC on #svn-dev is also
+appropriate for quick feedback before—but not instead of—mailing
+list discussion. If you ask on IRC, please wait some time for a response, as
+not everyone is online all the time (particularly on weekends).) That is so
+the community can express concerns with and suggest improvements for the
+proposed feature or implementation details as soon as possible—it is
+always better for all parties if that feedback is provided sooner (even before any code is written) rather than later.</p>
+
+</div> <!-- patches-writing -->
+
+<div class="h3" id="patches-submission">
+<h3>Submitting patches
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#patches-submission"
+ title="Link to this section">¶</a>
+</h3>
+
<p>Mail patches to dev@subversion.apache.org, starting the subject line with
<tt>[PATCH]</tt>. This helps our
<a href="<!--#echo var="GUIDE_ROLES_PAGE" -->#patch-manager">patch manager</a>
@@ -744,6 +773,8 @@ as well as the coding. Every patch need
through the process, and the person best qualified to do that is the
original submitter.</p>
+</div> <!-- patches-submission -->
+
</div> <!-- patches -->
</div> <!-- general -->