diff options
| author | Werner Lemberg <wl@gnu.org> | 2020-07-14 08:31:02 +0200 |
|---|---|---|
| committer | Werner Lemberg <wl@gnu.org> | 2020-07-14 08:31:21 +0200 |
| commit | 25a01e3b4793e958003d3a426a040a5c769ffbe5 (patch) | |
| tree | 5c1f99236a46ebcafa3e65bb78399f5fd759c7d0 | |
| parent | dd281ba75a20eb12710022b204aeee0465687362 (diff) | |
developer.html: Add section on submitting patches.
| -rw-r--r-- | developer.html | 50 |
1 files changed, 44 insertions, 6 deletions
diff --git a/developer.html b/developer.html index 9de40e4..b05abe7 100644 --- a/developer.html +++ b/developer.html @@ -123,11 +123,11 @@ </div> <p>When asked for a password, simply press Enter - for <tt>cvs login</tt>. The module names - are <tt>freetype</tt> (Freetype version 1.x, - C code), <tt>freetype1-contrib</tt> - (contributed programs), and <tt>ftpascal</tt> - (Freetype version 1.x, Pascal code).</p> + for <tt>cvs login</tt>. The module names + are <tt>freetype</tt> (Freetype version 1.x, + C code), <tt>freetype1-contrib</tt> (contributed + programs), and <tt>ftpascal</tt> (Freetype + version 1.x, Pascal code).</p> <p>The <tt>freetype2</tt> and <tt>ft2demos</tt> modules have been transformed to git (see above) and shouldn't @@ -157,6 +157,41 @@ <!-- ************************************************** --> + <div id="patches"> + <h2>Submitting Patches</h2> + + <p>Please submit patches to + the <a href="mailto:freetype-devel@nongnu.org">freetype-devel@nongnu.org</a> + mailing list – and thank you in advance for your + work on improving FreeType!<p> + + <p>Here are some tips on making your contribution easy to + integrate into the FreeType git repositories.</p> + + <ul> + <li> + In the preamble of your patch, add a description of your + changes similar to the entries in the <tt>ChangeLog</tt> + file. With ‘similar’ it is meant that the + format and style of <tt>ChangeLog</tt> entries should be + imitated as much as possible. However, don't modify + the <tt>ChangeLog</tt> file by yourself. + </li> + <li> + Try to follow the formatting of the source code as much + as possible. + </li> + <li> + If you plan to contribute larger changes, split them + into smaller, logical units. Reviewing code changes in + small, incremental steps is much easier to perform. + </li> + </ul> + </div> + + + <!-- ************************************************** --> + <div id="language-bindings"> <h2>Language Bindings</h2> @@ -338,7 +373,7 @@ <!-- ************************************************** --> <div class="updated"> - <p>Last update: 18-Jan-2019</p> + <p>Last update: 14-Jul-2020</p> </div> </div> </div> @@ -408,6 +443,9 @@ <a href="#bug-report">Bug Reports</a> </li> <li class="secondary"> + <a href="#patches">Submitting Patches</a> + </li> + <li class="secondary"> <a href="#language-bindings">Language Bindings</a> </li> <li class="secondary"> |