From: Eli Zaretskii <eliz@gnu.org>
To: John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH 4/4] Document support for 'info proc' on FreeBSD.
Date: Sat, 23 Dec 2017 08:46:00 -0000 [thread overview]
Message-ID: <83a7y9ltnm.fsf@gnu.org> (raw)
In-Reply-To: <20171222220513.54983-5-jhb@FreeBSD.org> (message from John Baldwin on Fri, 22 Dec 2017 14:05:13 -0800)
> From: John Baldwin <jhb@FreeBSD.org>
> Date: Fri, 22 Dec 2017 14:05:13 -0800
>
> gdb/doc/ChangeLog:
>
> * gdb.texinfo (Native): Rename subsection from SVR4 Process
> Information to Process Information.
> (Process Information): Document support for "info proc" on
> FreeBSD.
OK, with one comment:
> -@node SVR4 Process Information
> -@subsection SVR4 Process Information
> +@node Process Information
> +@subsection Process Information
This renaming must be done in the entire gdb.texinfo file, or else you
will get errors while producing the Info manual. I see at least one
more instance of the old name.
Thanks.
next prev parent reply other threads:[~2017-12-23 8:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 22:05 [PATCH 0/4] Support for 'info proc' on FreeBSD cores and native John Baldwin
2017-12-22 22:05 ` [PATCH 3/4] Support 'info proc' for native FreeBSD processes John Baldwin
2017-12-27 2:23 ` Simon Marchi
2018-01-03 19:05 ` John Baldwin
2018-01-03 19:13 ` Simon Marchi
2018-01-03 21:56 ` John Baldwin
2017-12-22 22:05 ` [PATCH 2/4] Support 'info proc' for FreeBSD process core dumps John Baldwin
2017-12-27 1:56 ` Simon Marchi
2018-01-03 19:05 ` John Baldwin
2017-12-22 22:05 ` [PATCH 1/4] Create psuedo sections for FreeBSD NT_PROCSTAT_(PROC|FILES|VMMAP) notes John Baldwin
2017-12-27 1:18 ` Simon Marchi
2018-01-02 11:49 ` Nick Clifton
2017-12-22 22:13 ` [PATCH 4/4] Document support for 'info proc' on FreeBSD John Baldwin
2017-12-23 8:46 ` Eli Zaretskii [this message]
2017-12-27 1:53 ` [PATCH 0/4] Support for 'info proc' on FreeBSD cores and native Simon Marchi
2018-01-03 19:05 ` John Baldwin
2018-01-03 19:15 ` Simon Marchi
2018-01-03 23:39 ` 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=83a7y9ltnm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
/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).