From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH v2] core(5): add more details for output paths and the crash handler
Date: Fri, 7 Oct 2016 22:50:50 +0200 [thread overview]
Message-ID: <d38e7196-abea-79a7-87aa-6c91c2a273ab@gmail.com> (raw)
In-Reply-To: <20161007191800.GX21655-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
On 10/07/2016 09:18 PM, Mike Frysinger wrote:
> On 07 Oct 2016 14:34, Michael Kerrisk (man-pages) wrote:
>> On 10/06/2016 07:24 PM, Mike Frysinger wrote:
>>> People sometimes assume that the crash handler runs in the same context
>>> as the crashing process. They would be incorrect :).
>>
>> Nice details to add to the page! Thanks for that. I've tweaked the
>> text a little, so you might want to take a look at my changes in
>> commit 4389c7abfffbe.
>
> looks fine. wrt /proc/PID vs /proc/[pid], i was using the form that
> core(5) already appeared to use. should all cases of /proc/PID be
> changed to /proc/[pid] in there ? there's both now ...
They should be consistent. I've done a sweep and fixed this
(to /proc/[pid]).
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-10-07 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 11:14 [PATCH] core(5): add more details for output paths and the crash handler Mike Frysinger
[not found] ` <20160928111450.32157-1-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2016-09-30 8:05 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkhFQnk=9k6J_mu8inhfFMaVwn=AhdH9xPg=HKG1OEiqyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-06 5:51 ` Michael Kerrisk (man-pages)
2016-10-06 17:24 ` [PATCH v2] " Mike Frysinger
[not found] ` <20161006172437.3329-1-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2016-10-07 12:34 ` Michael Kerrisk (man-pages)
[not found] ` <50b6faa5-d490-4a18-f2c5-87241fd0aeee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-10-07 19:18 ` Mike Frysinger
[not found] ` <20161007191800.GX21655-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
2016-10-07 20:50 ` Michael Kerrisk (man-pages) [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=d38e7196-abea-79a7-87aa-6c91c2a273ab@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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