Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: gdb-patches@sourceware.org,  tom@tromey.com
Subject: Re: [PATCH v2] * GDB Texinfo manual: Correctly reference Emacs facilities
Date: Sat, 14 Jun 2025 11:06:25 +0300	[thread overview]
Message-ID: <86wm9esq66.fsf@gnu.org> (raw)
In-Reply-To: <875xgzi8k8.fsf@jeremybryant.net> (message from Jeremy Bryant on Fri, 13 Jun 2025 23:24:39 +0100)

> From: Jeremy Bryant <jb@jeremybryant.net>
> Date: Fri, 13 Jun 2025 23:24:39 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Jeremy Bryant <jb@jeremybryant.net>
> >> Cc: gdb-patches@sourceware.org,  tom@tromey.com
> >> Date: Fri, 02 May 2025 22:04:56 +0100
> >> 
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> >> Date: Fri, 02 May 2025 09:20:43 +0300
> >> >> From: Eli Zaretskii <eliz@gnu.org>
> >> >> Cc: gdb-patches@sourceware.org, tom@tromey.com
> >> >> 
> >> >> > From: Jeremy Bryant <jb@jeremybryant.net>
> >> >> > Date: Thu, 01 May 2025 23:08:04 +0100
> >> >> 
> >> >> > More generally, I believe that this section predates the changes in
> >> >> > Emacs of M-x gdb vs M-x gud-gdb, so I will propose further patches down
> >> >> > the line.  (vc-annotate indicates the text hasn't been updated in a long
> >> >> > time)
> >> >> 
> >> >> In that case, I suggest to submit a single patch with all the changes
> >> >> together.  It will make the job of reviewing the patch easier.
> >> >
> >> > On second thought, perhaps the GDB manual should just mention the
> >> > Emacs front-end shortly, and point to the Emacs manual for the
> >> > details?  It is sub-optimal to have the GDB-related features described
> >> > in two manuals maintained by 23 different projects; doing that will
> >> > necessarily risk incompatibilities and inconsistencies.
> >> 
> >> OK, agree it is suboptimal to duplicate, and the existing text appears
> >> out-of-date (not updated in two decades).
> >> 
> >> I've revised the introduction, adapting styles from the previous section
> >> introduction and the current Emacs manual (30.1)
> >> 
> >> Revised patch, in-line, below.
> >> WDYT?
> >
> > LGTM, let's wait for your legal paperwork and install it then.
> 
> Thanks Eli, the legal paperwork has now come through, are you happy to
> commit the patch?

Done.

      parent reply	other threads:[~2025-06-14  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01 22:08 [PATCH] * GDB Texinfo manual: correct keyboard shortcut for gud-break in Emacs Jeremy Bryant
2025-05-02  6:20 ` Eli Zaretskii
2025-05-02  7:15   ` Eli Zaretskii
2025-05-02 21:04     ` [PATCH v2] * GDB Texinfo manual: Correctly reference Emacs facilities Jeremy Bryant
2025-05-10 10:29       ` Eli Zaretskii
     [not found]         ` <875xgzi8k8.fsf@jeremybryant.net>
2025-06-14  8:06           ` Eli Zaretskii [this message]

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=86wm9esq66.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jb@jeremybryant.net \
    --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