From: Jonny Grant <jg@jguk.org>
To: libc-alpha@sourceware.org
Subject: rt: Fix grammar in <sys/cdefs.h>
Date: Tue, 6 Oct 2020 23:42:38 +0100 [thread overview]
Message-ID: <32cdbe5b-a7be-75ad-6b53-734bb2337126@jguk.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 185 bytes --]
Hello
Two comments have words in not the right order, please find attached a patch to fix it.
ChangeLog:
2020-10-06 Jonny Grant <jg@jguk.org>
* sys/cdefs.h: Fix grammar
[-- Attachment #2: cdefs.h.patch --]
[-- Type: text/x-patch, Size: 877 bytes --]
--- cdefs.h.orig 2020-10-06 21:52:30.345175901 +0100
+++ cdefs.h 2020-10-06 23:36:13.604914244 +0100
@@ -25,7 +25,7 @@
/* The GNU libc does not support any K&R compilers or the traditional mode
of ISO C compilers anymore. Check for some of the combinations not
- anymore supported. */
+ supported anymore. */
#if defined __GNUC__ && !defined __STDC__
# error "You need a ISO C conforming compiler to use the glibc headers"
#endif
@@ -47,7 +47,7 @@
# endif
/* GCC can always grok prototypes. For C++ programs we add throw()
- to help it optimize the function calls. But this works only with
+ to help it optimize the function calls. But this only works with
gcc 2.8.x and egcs. For gcc 3.2 and up we even mark C functions
as non-throwing using a function attribute since programs can use
the -fexceptions options for C code as well. */
next reply other threads:[~2020-10-06 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 22:42 Jonny Grant [this message]
2020-10-07 0:02 ` rt: Fix grammar in <sys/cdefs.h> Zack Weinberg
2020-10-13 20:57 ` Jonny Grant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32cdbe5b-a7be-75ad-6b53-734bb2337126@jguk.org \
--to=jg@jguk.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).