diff options
| author | Eric Christopher <echristo@gmail.com> | 2015-12-10 21:47:38 +0000 |
|---|---|---|
| committer | Eric Christopher <echristo@gmail.com> | 2015-12-10 21:47:38 +0000 |
| commit | df2e4d2914098e7fa5eef500aa9894d042f1a39d (patch) | |
| tree | 83766ba6aa62cdfceb67c12e77d246e6bce0e23d | |
| parent | dedacf9c733a4e0465dd3045248d58b2191a458f (diff) | |
| download | bcm5719-llvm-df2e4d2914098e7fa5eef500aa9894d042f1a39d.tar.gz bcm5719-llvm-df2e4d2914098e7fa5eef500aa9894d042f1a39d.zip | |
More non-ascii quote characters.
llvm-svn: 255303
| -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 d357dd530b0..47c3b8b3d29 100644 --- a/llvm/docs/DeveloperPolicy.rst +++ b/llvm/docs/DeveloperPolicy.rst @@ -535,7 +535,7 @@ of the C++ API that it wraps. In practice, this means that things like "create debug info" or "create this type of instruction" are likely to be less stable than "take this IR file and JIT it for my current machine". -* Release stability: We won’t break the C API on the release branch with patches +* Release stability: We won't break the C API on the release branch with patches that go on that branch, with the exception that if we will fix an unintentional C API break that will keep the release consistent with both the previous and next release. @@ -549,7 +549,7 @@ that don't currently have one need to be discussed on the mailing list for desig 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 +release notes so that it's clear to external users who do not follow the project how the C API is changing and evolving. .. _copyright-license-patents: |
