From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2+rfc+doc] Install gcore by default (+new man page)
Date: Mon, 08 Apr 2013 19:41:00 -0000 [thread overview]
Message-ID: <83r4ilawlx.fsf@gnu.org> (raw)
In-Reply-To: <20130407185443.GB15389@host2.jankratochvil.net>
> Date: Sun, 7 Apr 2013 20:54:43 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> +Produced file is equivalent to a kernel produced core file as if the process
> +crashed (and also it had to have @command{ulimit -c} enabled appropriately).
Suggest to reword in parentheses:
(and if @kbd{ulimit -c} were used to set up an appropriate core dump
limit)
Note: @kbd, not @command, as the latter is for command names, not for
command lines.
> +Contrary to it after @command{gcore} the program remains running without any
> +change.
"Unlike after a crash, after @command{gcore} the program ..."
The documentation part is OK with these changes.
Thanks.
next prev parent reply other threads:[~2013-04-08 15:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 14:15 Jan Kratochvil
2013-04-08 19:41 ` Eli Zaretskii [this message]
2013-04-09 2:10 ` Jan Kratochvil
2013-04-09 8:53 ` Tom Tromey
2013-04-09 9:01 ` Jan Kratochvil
2013-04-09 14:26 ` Jan Kratochvil
2013-04-09 18:53 ` Eli Zaretskii
2013-04-09 15:29 ` Pedro Alves
2013-04-09 19:59 ` Jan Kratochvil
2013-04-10 19:49 ` Pedro Alves
2013-04-11 2:43 ` Jan Kratochvil
2013-04-11 7:40 ` Jan Kratochvil
2013-04-11 17:52 ` auto-generated parts in posted patches (Re: [patch 2/2+rfc+doc] Install gcore by default (+new man page)) Pedro Alves
2013-04-12 18:16 ` Tom Tromey
2013-04-11 17:49 ` [patch 2/2+rfc+doc] Install gcore by default (+new man page) Pedro Alves
2013-04-11 22:59 ` [commit] " Jan Kratochvil
2013-04-11 23:00 ` Pedro Alves
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=83r4ilawlx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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