From: Gerald Pfeifer <gerald@pfeifer.com>
To: Michael Witten <mfwitten@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/4] Docs: extend.texi: Add missing semicolon for consistency
Date: Wed, 08 Apr 2015 19:13:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1504082110490.9357@tuna.site> (raw)
In-Reply-To: <1370549d-0ad8-4e6a-92bf-0dcc6a6eb789-mfwitten@gmail.com>
Hi Michael,
and big apologies for this falling through a lot of cracks
apparently. I just committed your patch with the ChangeLog
below.
If there are any other patches that have not been committed
(nor NACKed yet, I know there were some as well), please let
us know and I will look into getting at least documentation
patches addressed swiftly going forward.
Thank you, and sorry again,
Gerald
2015-04-08 Michael Witten <mfwitten@gmail.com>
* doc/extend.texi (Attribute Syntax): Add a trailing semicolon
to an example.
Index: doc/extend.texi
===================================================================
--- doc/extend.texi (revision 221930)
+++ doc/extend.texi (working copy)
@@ -4771,7 +4771,7 @@
@smallexample
__attribute__((noreturn)) void d0 (void),
__attribute__((format(printf, 1, 2))) d1 (const char *, ...),
- d2 (void)
+ d2 (void);
@end smallexample
@noindent
On Wed, 27 Apr 2011, Michael Witten wrote:
> ---
> trunk/gcc/doc/extend.texi | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/trunk/gcc/doc/extend.texi b/trunk/gcc/doc/extend.texi
> index eddff95..c154958 100644
> --- a/trunk/gcc/doc/extend.texi
> +++ b/trunk/gcc/doc/extend.texi
> @@ -3997,7 +3997,7 @@
> @smallexample
> __attribute__((noreturn)) void d0 (void),
> __attribute__((format(printf, 1, 2))) d1 (const char *, ...),
> - d2 (void)
> + d2 (void);
> @end smallexample
>
> @noindent
next prev parent reply other threads:[~2015-04-08 19:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 1:22 [PATCH 0/4] Docs: extend.texi Michael Witten
2011-04-28 1:30 ` [PATCH 1/4] Docs: extend.texi: Add missing semicolon for consistency Michael Witten
2015-04-08 19:13 ` Gerald Pfeifer [this message]
2015-04-12 1:14 ` Michael Witten
2015-04-12 20:22 ` Gerald Pfeifer
2011-04-28 1:34 ` [PATCH 2/4] Docs: extend.texi: Remove trailing blanks from lines Michael Witten
2011-05-03 20:56 ` Gerald Pfeifer
2011-05-04 6:31 ` Michael Witten
2011-05-04 18:05 ` Mike Stump
2011-05-04 18:39 ` Nathan Froyd
2011-05-04 10:13 ` Joseph S. Myers
2011-05-04 18:34 ` Mike Stump
2011-05-04 18:38 ` Joseph S. Myers
2011-05-04 18:42 ` Gerald Pfeifer
2011-05-04 18:58 ` Joseph S. Myers
2011-05-04 23:57 ` Mike Stump
2011-05-05 0:15 ` Mike Stump
2011-05-05 9:42 ` Richard Guenther
2011-05-05 18:12 ` Michael Witten
2011-04-28 1:36 ` [PATCH 4/4] Docs: extend.texi: Reword and rearrange attribute node introductions Michael Witten
2011-04-28 1:38 ` [PATCH 3/4] Docs: extend.texi: Rearrange nodes; no text was removed or added Michael Witten
2011-05-21 12:24 ` [PATCH 0/4] Docs: extend.texi Michael Witten
2011-06-10 2:06 ` Michael Witten
2011-06-20 17:20 ` Michael Witten
2011-06-23 8:00 ` Michael Witten
2011-06-27 21:18 ` Michael Witten
2011-06-27 21:36 ` Michael Witten
2011-06-30 22:34 ` Michael Witten
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.20.1504082110490.9357@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mfwitten@gmail.com \
/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).