From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simark@simark.ca>
Cc: mhw@netris.org, bug-gdb@gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] doc: fix false claim about second argument to gdb (was: Manual contradicts itself regarding second command line argument)
Date: Tue, 18 Jun 2019 16:14:00 -0000 [thread overview]
Message-ID: <83zhmeswfl.fsf@gnu.org> (raw)
In-Reply-To: <b3fcb2b4-bf5d-4fde-2a10-589630c79450@simark.ca> (message from Simon Marchi on Tue, 18 Jun 2019 10:51:03 -0400)
> From: Simon Marchi <simark@simark.ca>
> Date: Tue, 18 Jun 2019 10:51:03 -0400
>
> -You can, instead, specify a process ID as a second argument, if you want
> -to debug a running process:
> +You can, instead, specify a process ID as a second argument or using option
> +@code{-p}, if you want to debug a running process:
"specify ... or using ..." is incorrect English. I guess you meant
"use"?
No other comments, thanks. (I didn't look at the code to see if the
description is factually correct.)
next prev parent reply other threads:[~2019-06-18 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87imt321yr.fsf@netris.org>
2019-06-18 14:51 ` Simon Marchi
2019-06-18 16:14 ` Eli Zaretskii [this message]
2019-06-18 16:40 ` [PATCH] doc: fix false claim about second argument to gdb Simon Marchi
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=83zhmeswfl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gdb@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mhw@netris.org \
--cc=simark@simark.ca \
/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