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

Don't attribute in file headers anymore. See llvmdev for the

Browse Source 
discussion of this change.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@45409 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner 2007-12-29 19:56:08 +00:00
parent a5e90d7b74
commit ab2b10c3a9
2 changed files with 12 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/CodingStandards.html
View File

@ -134,8 +134,8 @@ this:</p>
// //
// The LLVM Compiler Infrastructure // The LLVM Compiler Infrastructure
// //
// This file was developed by &lt;whoever started the file&gt; and is distributed under // This file is distributed under the University of Illinois Open Source
// the University of Illinois Open Source License. See LICENSE.TXT for details. // License. See LICENSE.TXT for details.
// //
//===----------------------------------------------------------------------===// //===----------------------------------------------------------------------===//
// //
@ -146,9 +146,7 @@ this:</p>
</pre> </pre>
</div> </div>
<p>A few things to note about this particular format: The 'developed by' line <p>A few things to note about this particular format: The "<tt>-*- C++
should be the name of the person or organization who initially contributed the
file. The "<tt>-*- C++
-*-</tt>" string on the first line is there to tell Emacs that the source file -*-</tt>" string on the first line is there to tell Emacs that the source file
is a C++ file, not a C file (Emacs assumes .h files are C files by default). is a C++ file, not a C file (Emacs assumes .h files are C files by default).
Note that this tag is not necessary in .cpp files. The name of the file is also Note that this tag is not necessary in .cpp files. The name of the file is also
@ -156,9 +154,9 @@ on the first line, along with a very short description of the purpose of the
file. This is important when printing out code and flipping though lots of file. This is important when printing out code and flipping though lots of
pages.</p> pages.</p>
<p>The next section in the file is a concise note that defines the license that <p>The next section in the file is a concise note that defines the license
the file is released under. This makes it perfectly clear what terms the source that the file is released under. This makes it perfectly clear what terms the
code can be distributed under.</p> source code can be distributed under and should not be modified in any way.</p>
<p>The main body of the description does not have to be very long in most cases. <p>The main body of the description does not have to be very long in most cases.
Here it's only two lines. If an algorithm is being implemented or something Here it's only two lines. If an algorithm is being implemented or something

28
docs/DeveloperPolicy.html
View File

@ -417,28 +417,12 @@ Changes</a></div>
<div class="doc_text"> <div class="doc_text">
<p>We believe in correct attribution of contributions to <p>We believe in correct attribution of contributions to
their contributors. However, we do not want the source code to be littered their contributors. However, we do not want the source code to be littered
with random attributions (this is noisy/distracting and revision control with random attributions "this code written by J Random Guy" (this is noisy
keeps a perfect history of this anyway). As such, we follow these rules:</p> and distracting. In practice, the revision control system keeps a perfect
<ol> history of who change what, and the CREDITS.txt file describes higher-level
<li>Developers who originate new files in LLVM should place their name at contributions.</p>
the top of the file per the
<a href="CodingStandards.html#scf_commenting">Coding Standards</a>.</li> <p>Overall, please do not add contributor names to the source base.</p>
<li>There should be only one name at the top of the file and it should be
the person who created the file.</li>
<li>Placing your name in the file does not imply <a
href="#clp">copyright</a>: it is only used to attribute the file to
its original author.</li>
<li>Developers should be aware that after some time has passed, the name at
the top of a file may become meaningless as maintenance/ownership of files
changes. Despite this, once set, the attribution of a file never changes.
Revision control keeps an accurate history of contributions.</li>
<li>Developers should maintain their entry in the
<a href="http://llvm.org/svn/llvm-project/llvm/trunk/CREDITS.TXT">CREDITS.txt</a>
file to summarize their contributions.</li>
<li>Commit comments should contain correct attribution of the person who
submitted the patch if that person is not the committer (i.e. when a
developer with commit privileges commits a patch for someone else).</li>
</ol>
</div> </div>