From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] gdb manual: Cygwin => Windows
Date: Fri, 08 May 2026 16:08:20 +0300 [thread overview]
Message-ID: <86y0hu59rv.fsf@gnu.org> (raw)
In-Reply-To: <d44806ef-3374-4a09-8851-a2704ff024f9@palves.net> (message from Pedro Alves on Thu, 7 May 2026 18:42:27 +0100)
> Date: Thu, 7 May 2026 18:42:27 +0100
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <pedro@palves.net>
>
> On 2026-05-04 20:18, Eli Zaretskii wrote:
> >> From: Pedro Alves <pedro@palves.net>>
> >> +The following commands are available in all native Windows
> >> +configurations, including Cygwin:
> >
> > "Windows native" generally excludes Cygwin, because Cygwin uses a
> > different runtime.
>
> Indeed.
>
> > So maybe instead of saying "all native Windows,
> > including Cygwin" we should say "all native Windows configuration, and
> > also Cygwin"? If you agree with that, then the rest of the text you
> > added and the section name should also be amended.
> >
> >> +In addition, the following commands are available on Cygwin:
> > ^^^^^^^^^^^^^^^^^^^
> > You mean, "available only when debugging Cygwin programs"?
> >
> > Reviewed-By: Eli Zaretskii <eliz@gnu.org>
> >
> How about this? It splits the node in two, with cross links.
LGTM, thanks.
next prev parent reply other threads:[~2026-05-08 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 17:33 [PATCH 0/3] Show CONTEXT_EXCEPTION_REQUEST info in "info threads" Pedro Alves
2026-05-04 17:33 ` [PATCH 1/3] Windows gdb: " Pedro Alves
2026-05-04 19:12 ` Eli Zaretskii
2026-05-04 17:33 ` [PATCH 2/3] gdb manual: Cygwin => Windows Pedro Alves
2026-05-04 19:18 ` Eli Zaretskii
2026-05-07 17:42 ` Pedro Alves
2026-05-08 13:08 ` Eli Zaretskii [this message]
2026-05-04 17:33 ` [PATCH 3/3] Windows gdb: Document "info threads" Windows specifics Pedro Alves
2026-05-04 19:14 ` Eli Zaretskii
2026-05-07 17:59 ` Pedro Alves
2026-05-08 13:12 ` Eli Zaretskii
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=86y0hu59rv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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