r203259 - "Mac OS/X" -> "Mac OS X" spelling fixes for clang.

[Alexander Potapenko]

I thought the official name is just "OS X" now, isn't it?
On Mar 7, 2014 10:20 PM, "Nico Weber" <nicolasweber at gmx.de> wrote:

> Author: nico
> Date: Fri Mar  7 12:09:57 2014
> New Revision: 203259
>
> URL: http://llvm.org/viewvc/llvm-project?rev=203259&view=rev
> Log:
> "Mac OS/X" -> "Mac OS X" spelling fixes for clang.
>
> Patch from Sean McBride <sean at rogue-research.com>!
>
> Modified:
>     cfe/trunk/docs/UsersManual.rst
>     cfe/trunk/docs/tools/clang.pod
>     cfe/trunk/www/features.html
>
> Modified: cfe/trunk/docs/UsersManual.rst
> URL:
> http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/UsersManual.rst?rev=203259&r1=203258&r2=203259&view=diff
>
> ==============================================================================
> --- cfe/trunk/docs/UsersManual.rst (original)
> +++ cfe/trunk/docs/UsersManual.rst Fri Mar  7 12:09:57 2014
> @@ -762,7 +762,7 @@ on-disk cache that contains the vital in
>  some of the work needed to process a corresponding header file. While
>  details of precompiled headers vary between compilers, precompiled
>  headers have been shown to be highly effective at speeding up program
> -compilation on systems with very large system headers (e.g., Mac OS/X).
> +compilation on systems with very large system headers (e.g., Mac OS X).
>
>  Generating a PCH File
>  ^^^^^^^^^^^^^^^^^^^^^
> @@ -1358,7 +1358,7 @@ X86
>  ^^^
>
>  The support for X86 (both 32-bit and 64-bit) is considered stable on
> -Darwin (Mac OS/X), Linux, FreeBSD, and Dragonfly BSD: it has been tested
> +Darwin (Mac OS X), Linux, FreeBSD, and Dragonfly BSD: it has been tested
>  to correctly compile many large C, C++, Objective-C, and Objective-C++
>  codebases.
>
> @@ -1413,7 +1413,7 @@ backend.
>  Operating System Features and Limitations
>  -----------------------------------------
>
> -Darwin (Mac OS/X)
> +Darwin (Mac OS X)
>  ^^^^^^^^^^^^^^^^^
>
>  None
>
> Modified: cfe/trunk/docs/tools/clang.pod
> URL:
> http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/tools/clang.pod?rev=203259&r1=203258&r2=203259&view=diff
>
> ==============================================================================
> --- cfe/trunk/docs/tools/clang.pod (original)
> +++ cfe/trunk/docs/tools/clang.pod Fri Mar  7 12:09:57 2014
> @@ -237,7 +237,7 @@ Specify the architecture to build for.
>
>  =item B<-mmacosx-version-min>=I<version>
>
> -When building for Mac OS/X, specify the minimum version supported by your
> +When building for Mac OS X, specify the minimum version supported by your
>  application.
>
>  =item B<-miphoneos-version-min>
>
> Modified: cfe/trunk/www/features.html
> URL:
> http://llvm.org/viewvc/llvm-project/cfe/trunk/www/features.html?rev=203259&r1=203258&r2=203259&view=diff
>
> ==============================================================================
> --- cfe/trunk/www/features.html (original)
> +++ cfe/trunk/www/features.html Fri Mar  7 12:09:57 2014
> @@ -69,7 +69,7 @@ options for performance analysis.</p>
>
>  <p>While there is still much that can be done, we find that the clang
> front-end
>  is significantly quicker than gcc and uses less memory  For example, when
> -compiling "Carbon.h" on Mac OS/X, we see that clang is 2.5x faster than
> GCC:</p>
> +compiling "Carbon.h" on Mac OS X, we see that clang is 2.5x faster than
> GCC:</p>
>
>  <img class="img_slide" src="feature-compile1.png" width="400" height="300"
>       alt="Time to parse carbon.h: -fsyntax-only">
>
>
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20140308/00f60b85/attachment.html>