RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2025-04-11 10:31:27 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix typos in a document; NFC

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@308331 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Hiroshi Inoue 2017-07-18 17:52:47 +00:00
parent e9ec240bfb
commit 4ea9a7811e
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/CodingStandards.rst
View File

@ -34,10 +34,10 @@ There are some conventions that are not uniformly followed in the code base
(e.g. the naming convention). This is because they are relatively new, and a (e.g. the naming convention). This is because they are relatively new, and a
lot of code was written before they were put in place. Our long term goal is lot of code was written before they were put in place. Our long term goal is
for the entire codebase to follow the convention, but we explicitly *do not* for the entire codebase to follow the convention, but we explicitly *do not*
want patches that do large-scale reformating of existing code. On the other want patches that do large-scale reformatting of existing code. On the other
hand, it is reasonable to rename the methods of a class if you're about to hand, it is reasonable to rename the methods of a class if you're about to
change it in some other way. Just do the reformating as a separate commit from change it in some other way. Just do the reformatting as a separate commit
the functionality change. from the functionality change.
The ultimate goal of these guidelines is to increase the readability and The ultimate goal of these guidelines is to increase the readability and
maintainability of our common source base. If you have suggestions for topics to maintainability of our common source base. If you have suggestions for topics to