Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ivo Raisr <ivo.raisr@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Bug 20936 - documentation review
Date: Tue, 31 Jan 2017 15:32:00 -0000	[thread overview]
Message-ID: <83k29bw8i3.fsf@gnu.org> (raw)
In-Reply-To: <461e5cd3-fadc-7881-154f-c53f66b2301e@oracle.com> (message from	Ivo Raisr on Tue, 31 Jan 2017 05:47:19 +0100)

> From: Ivo Raisr <ivo.raisr@oracle.com>
> Date: Tue, 31 Jan 2017 05:47:19 +0100
> 
> Please can I get a documentation review for the attached patch.
> The affected documentation files are:
> gdb/doc/gdb.texinfo
> 
> The patch has been successfully review by Yao Qi <qiyaoltc@gmail.com>.

Sorry for not responding earlier.

The patch for gdb.texinfo is okay, but I don't see the ChangeLog
entries.  And what about NEWS?

Thanks.


  reply	other threads:[~2017-01-31 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31  4:47 Ivo Raisr
2017-01-31 15:32 ` Eli Zaretskii [this message]
2017-01-31 21:57   ` Ivo Raisr
2017-02-01  3:33     ` Eli Zaretskii
2017-02-06  7:49       ` Jose E. Marchesi

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=83k29bw8i3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ivo.raisr@oracle.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