Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 8/8] Update "save gdb-index" documentation
Date: Thu, 01 Aug 2019 02:36:00 -0000	[thread overview]
Message-ID: <831ry5ipcj.fsf@gnu.org> (raw)
In-Reply-To: <20190731201411.8044-9-tromey@adacore.com> (message from Tom	Tromey on Wed, 31 Jul 2019 14:14:11 -0600)

> From: Tom Tromey <tromey@adacore.com>
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Wed, 31 Jul 2019 14:14:11 -0600
> 
> This updates the "save gdb-index" documentation to reflect the new
> state of Ada support.  It also corrects an existing grammatical error.
> 
> gdb/doc/ChangeLog
> 2019-07-31  Tom Tromey  <tromey@adacore.com>
> 
> 	* gdb.texinfo (Index Files): Update Ada text.

OK, thanks.


  reply	other threads:[~2019-08-01  2:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 20:14 [PATCH 0/8] Add Ada support for .debug_names Tom Tromey
2019-07-31 20:14 ` [PATCH 2/8] Change iterate_over_symbols to return bool Tom Tromey
2019-07-31 20:14 ` [PATCH 6/8] Add Ada support for .debug_names Tom Tromey
2019-07-31 20:14 ` [PATCH 7/8] Add Ada support to cc-with-tweaks.exp Tom Tromey
2019-07-31 20:14 ` [PATCH 1/8] Change map_matching_symbols to take a symbol_found_callback_ftype Tom Tromey
2019-07-31 20:14 ` [PATCH 3/8] Simplify psym_map_matching_symbols Tom Tromey
2019-07-31 20:14 ` [PATCH 8/8] Update "save gdb-index" documentation Tom Tromey
2019-08-01  2:36   ` Eli Zaretskii [this message]
2019-07-31 20:22 ` [PATCH 4/8] Change map_matching_symbols to take a lookup_name_info Tom Tromey
2019-07-31 20:22 ` [PATCH 5/8] Fix latent bug in .debug_names file-name handling Tom Tromey
2019-09-10 14:22 ` [PATCH 0/8] Add Ada support for .debug_names Tom Tromey

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=831ry5ipcj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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