From: Eli Zaretskii <eliz@gnu.org>
To: luisgpm@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Improve printf DFP support
Date: Wed, 09 Jan 2008 04:14:00 -0000 [thread overview]
Message-ID: <uve63skit.fsf@gnu.org> (raw)
In-Reply-To: <1199837025.22083.13.camel@gargoyle> (message from Luis Machado on Tue, 08 Jan 2008 22:03:44 -0200)
> From: Luis Machado <luisgpm@linux.vnet.ibm.com>
> Cc: gdb-patches@sourceware.org
> Date: Tue, 08 Jan 2008 22:03:44 -0200
>
> > Thanks. The documentation part of the patch is approved, but please
> > include in the ChangeLog entry the name of the node where you make the
> > change, as if it were a function.
>
> Thanks. Like so?
Yes, thanks.
next prev parent reply other threads:[~2008-01-09 4:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 13:28 Luis Machado
2008-01-08 15:19 ` Thiago Jung Bauermann
2008-01-08 15:29 ` Daniel Jacobowitz
2008-01-08 23:54 ` Jim Blandy
2008-01-08 15:29 ` Luis Machado
2008-01-08 20:42 ` Eli Zaretskii
2008-01-09 0:04 ` Luis Machado
2008-01-09 4:14 ` Eli Zaretskii [this message]
2008-01-09 12:52 ` Daniel Jacobowitz
2008-01-09 13:51 ` Luis Machado
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=uve63skit.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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