diff options
author | Eric Christopher <echristo@gmail.com> | 2015-12-10 21:46:24 +0000 |
---|---|---|
committer | Eric Christopher <echristo@gmail.com> | 2015-12-10 21:46:24 +0000 |
commit | dedacf9c733a4e0465dd3045248d58b2191a458f (patch) | |
tree | 348d67add3bf4fdd9343ea9acbd3003ab6f28feb | |
parent | b5c2b8dc92b09bddcbf63d75cba5cbc0bb9f43cd (diff) | |
download | bcm5719-llvm-dedacf9c733a4e0465dd3045248d58b2191a458f.tar.gz bcm5719-llvm-dedacf9c733a4e0465dd3045248d58b2191a458f.zip |
Clarify some of the wording on adding a new subcomponent to the
C API.
llvm-svn: 255302
-rw-r--r-- | llvm/docs/DeveloperPolicy.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/DeveloperPolicy.rst b/llvm/docs/DeveloperPolicy.rst index 5a83f5e43a8..d357dd530b0 100644 --- a/llvm/docs/DeveloperPolicy.rst +++ b/llvm/docs/DeveloperPolicy.rst @@ -545,8 +545,8 @@ other patch. * Including new things into the API: If an LLVM subcomponent has a C API already included, then expanding that C API is acceptable. Adding C API for subcomponents -that don't currently have one is fine, and the details of how best to design that -API should be discussed on the mailing list. +that don't currently have one need to be discussed on the mailing list for design +and maintainability feedback prior to implementation. * Documentation: Any changes to the C API are required to be documented in the release notes so that it’s clear to external users who do not follow the project |