From: Andreas Jaeger <aj@suse.de>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Ian Lance Taylor <ian@airs.com>, Eli Zaretskii <eliz@gnu.org>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix deftypefn in fopen_unlocked.c
Date: Sun, 15 May 2005 18:08:00 -0000 [thread overview]
Message-ID: <m37ji0l7k7.fsf@gromit.moeb> (raw)
In-Reply-To: <Pine.LNX.4.61.0505151724350.3466@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Sun, 15 May 2005 17:25:15 +0000 (UTC)")
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
"Joseph S. Myers" <joseph@codesourcery.com> writes:
> On Sun, 15 May 2005, Andreas Jaeger wrote:
>
>> Ian Lance Taylor <ian@airs.com> writes:
>>
>> > "Eli Zaretskii" <eliz@gnu.org> writes:
>> >
>> >> More of the same:
>> >>
>> >> 2005-05-14 Eli Zaretskii <eliz@gnu.org>
>> >>
>> >> * fopen_unlocked.c: Enclose multi-word data types in @deftypefn in
>> >> braces.
>> >
>> > This is OK. Thanks.
>>
>> Committed to GCC mainline,
>
> functions.texi should be regenerated when committing this patches (and it
> should be verified that the new functions.texi does indeed pass "make
> info" and "make dvi" before committing it).
Ok, will take care of it,
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2005-05-15 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 9:23 Eli Zaretskii
2005-05-15 16:37 ` Ian Lance Taylor
2005-05-15 17:04 ` Andreas Jaeger
2005-05-15 17:44 ` Joseph S. Myers
2005-05-15 18:08 ` Andreas Jaeger [this message]
2005-05-15 19:46 ` Eli Zaretskii
2005-05-15 20:16 ` Joseph S. Myers
2005-05-15 22:09 ` Eli Zaretskii
2005-05-15 22:05 ` Andreas Jaeger
2005-05-16 1:24 ` Eli Zaretskii
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=m37ji0l7k7.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ian@airs.com \
--cc=joseph@codesourcery.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