6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-03-03 14:31:10 +00:00
Code Issues Projects Releases Wiki Activity

fix TOC, clarify bullet in incremental dev

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34407 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner 2007-02-19 05:59:30 +00:00
parent 1653fec412
commit 8bb16ff2bb
1 changed files with 6 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/DeveloperPolicy.html
View File

@ -24,13 +24,6 @@
</ol></li> </ol></li>
<li><a href="#attribution">Attribution of Changes</a></li> <li><a href="#attribution">Attribution of Changes</a></li>
</ol></li> </ol></li>
<li><a href="#patches">Patch Policies</a>
<ol>
<li><a href="#p_form">Patch Form</a></li>
<li><a href="#p_submission">Patch Submission</a></li>
<li><a href="#p_aftersub">After Submission</a></li>
<li><a href="#p_aftercommit">After Commit</a></li>
</ol></li>
<li><a href="#candl">Copyright and License</a> <li><a href="#candl">Copyright and License</a>
<ol> <ol>
<li><a href="#copyright">Copyright</a></li> <li><a href="#copyright">Copyright</a></li>
@ -310,12 +303,15 @@ quality patches. If you would like commit access, please send an email to the
<li>The remaining inter-related work should be decomposed into unrelated <li>The remaining inter-related work should be decomposed into unrelated
sets of changes if possible. Once this is done, define the first increment sets of changes if possible. Once this is done, define the first increment
and get consensus on what the end goal of the change is.</li> and get consensus on what the end goal of the change is.</li>
<li>Increments can be stand alone (e.g. to fix a bug), or part of a planned
series of increments towards some development goal.</li> <li>Each change in the set can be stand alone (e.g. to fix a bug), or part
<li>Increments should be kept as small as possible. This simplifies your of a planned series of changes that works towards the development goal.</li>
<li>Each change should be kept as small as possible. This simplifies your
work (into a logical progression), simplifies code review and reduces the work (into a logical progression), simplifies code review and reduces the
chance that you will get negative feedback on the change. Small increments chance that you will get negative feedback on the change. Small increments
also facilitate the maintenance of a high quality code base.</li> also facilitate the maintenance of a high quality code base.</li>
<li>Often, an independent precursor to a big change is to add a new API and <li>Often, an independent precursor to a big change is to add a new API and
slowly migrate clients to use the new API. Each change to use the new slowly migrate clients to use the new API. Each change to use the new
API is often "obvious" and can be committed without review. Once the API is often "obvious" and can be committed without review. Once the