public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 29/29] Document new Python and Guile constants
Date: Tue, 23 Jan 2024 20:11:34 +0200	[thread overview]
Message-ID: <86cytr6ht5.fsf@gnu.org> (raw)
In-Reply-To: <8734uosx93.fsf@tromey.com> (message from Tom Tromey on Mon, 22 Jan 2024 17:34:48 -0700)

> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
> Date: Mon, 22 Jan 2024 17:34:48 -0700
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Tom Tromey <tom@tromey.com>
> >> Date: Mon, 20 Nov 2023 20:54:00 -0700
> >> 
> >> This documents the new Python and Guile constants introduced earlier
> >> in this series.
> 
> Eli> Thanks.
> 
> ...
> 
> Eli> I suggest an example here to explain what is a "type using a tag"; it
> Eli> was not clear to me, FWIW.
> 
> ...
> 
> I missed this review before sending v2.
> I've updated the doc patch.  The new version is appended, let me know
> what you think.

This is fine, thanks.

Approved-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2024-01-23 18:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21  3:53 [PATCH 00/29] Restructure symbol domains Tom Tromey
2023-11-21  3:53 ` [PATCH 01/29] Fix bug in cooked index scanner Tom Tromey
2023-11-21  3:53 ` [PATCH 02/29] Small cleanup in DWARF reader Tom Tromey
2023-11-21  3:53 ` [PATCH 03/29] Make nsalias.exp more reliable Tom Tromey
2023-11-21  3:53 ` [PATCH 04/29] Fix latent bug in mdebugread.c Tom Tromey
2023-11-21  3:53 ` [PATCH 05/29] Give names to unspecified types Tom Tromey
2023-11-21  3:53 ` [PATCH 06/29] Remove NR_DOMAINS Tom Tromey
2023-11-21  3:53 ` [PATCH 07/29] Simplify symbol_to_info_string Tom Tromey
2023-11-21  3:53 ` [PATCH 08/29] Split up a big 'if' in symtab.c Tom Tromey
2023-11-21  3:53 ` [PATCH 09/29] Use a .def file for domain_enum Tom Tromey
2023-11-21  3:53 ` [PATCH 10/29] Add two new symbol domains Tom Tromey
2023-11-21  3:53 ` [PATCH 11/29] Add domain_search_flags Tom Tromey
2023-11-21  3:53 ` [PATCH 12/29] Replace search_domain with domain_search_flags Tom Tromey
2023-11-21  3:53 ` [PATCH 13/29] Remove a check of VAR_DOMAIN Tom Tromey
2023-11-21  3:53 ` [PATCH 14/29] Introduce "scripting" domains Tom Tromey
2023-11-21  3:53 ` [PATCH 15/29] Use domain_search_flags in lookup_global_symbol_language Tom Tromey
2023-11-21  3:53 ` [PATCH 16/29] Use domain_search_flags in lookup_symbol et al Tom Tromey
2023-11-21  3:53 ` [PATCH 17/29] Remove some obsolete Python constants Tom Tromey
2023-11-21  3:53 ` [PATCH 18/29] Remove old symbol_matches_domain Tom Tromey
2023-11-21  3:53 ` [PATCH 19/29] Use the new symbol domains Tom Tromey
2023-11-21  3:53 ` [PATCH 20/29] Simplify some symbol searches in Ada code Tom Tromey
2023-11-21  3:53 ` [PATCH 21/29] Simplify some symbol searches in linespec.c Tom Tromey
2023-11-21  3:53 ` [PATCH 22/29] Only search for "main" as a function Tom Tromey
2023-11-21  3:53 ` [PATCH 23/29] Only look for functions in expand_symtabs_for_function Tom Tromey
2023-11-21  3:53 ` [PATCH 24/29] Use a function-domain search in inside_main_func Tom Tromey
2023-11-21  3:53 ` [PATCH 25/29] Only search types in cp_lookup_rtti_type Tom Tromey
2023-11-21  3:53 ` [PATCH 26/29] Only search types in lookup_typename Tom Tromey
2023-11-21  3:53 ` [PATCH 27/29] Only search for functions in rust_structop::evaluate_funcall Tom Tromey
2023-11-21  3:53 ` [PATCH 28/29] Refine search in cp_search_static_and_baseclasses Tom Tromey
2023-11-21  3:54 ` [PATCH 29/29] Document new Python and Guile constants Tom Tromey
2023-11-21 11:39   ` Eli Zaretskii
2024-01-23  0:34     ` Tom Tromey
2024-01-23 18:11       ` Eli Zaretskii [this message]
2023-11-21 18:37 ` [PATCH 00/29] Restructure symbol domains John Baldwin

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=86cytr6ht5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).