From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: man-pages-3.37 is released
Date: Sat, 24 Mar 2012 11:55:43 +1300 [thread overview]
Message-ID: <CAKgNAkhcFM66i_RoxB+AV9yViYRVLBfiMDsO=q8wY0spAL=Ubg@mail.gmail.com> (raw)
In-Reply-To: <CAK1hOcPVYcJan5=fbhz3T0FRZOwGUpFVxfY45r9ST50MqOpk7Q@mail.gmail.com>
On Sat, Mar 24, 2012 at 1:51 AM, Denys Vlasenko
<vda.linux@googlemail.com> wrote:
> Hi Michael,
>
> On Mon, Mar 19, 2012 at 7:29 PM, Michael Kerrisk (man-pages)
> <mtk.manpages@gmail.com> wrote:
>> On Sat, Mar 17, 2012 at 1:16 PM, Denys Vlasenko
>> <vda.linux@googlemail.com> wrote:
>>> On Friday 09 March 2012 18:27, Michael Kerrisk (man-pages) wrote:
>>>> ptrace.2
>>>> Denys Vlasenko [Oleg Nesterov, Tejun Heo]
>>>> add extended description of various ptrace quirks
>>>
>>> Pulled current git and spotted a few broken places.
>>
>> I made a few light edits to your patch, but basically applied it as
>> given for man-pages-3.38.
>
> Thanks! I found one tiny markup bug.
>
> Also, I want to add info about PTRACE_GETEVENTMSG on
> PTRACE_EVENT_EXEC. We document PTRACE_GETEVENTMSG
> on all other PTRACE_EVENT_foo's, except EXEC.
> That's not fair :)
>
> Please find the patch attached.
Thanks Denys. Applied for 3.38. ptrace.2 keeps getting better and better!
I appreciate that you like send the patch as an attachment so it
arrives intact, but it'd be helpful for review if you *also* posted a
copy inline.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
prev parent reply other threads:[~2012-03-23 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 17:27 man-pages-3.37 is released Michael Kerrisk (man-pages)
2012-03-17 0:16 ` Denys Vlasenko
2012-03-19 18:29 ` Michael Kerrisk (man-pages)
2012-03-23 12:51 ` Denys Vlasenko
2012-03-23 22:55 ` 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='CAKgNAkhcFM66i_RoxB+AV9yViYRVLBfiMDsO=q8wY0spAL=Ubg@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda.linux@googlemail.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;
as well as URLs for NNTP newsgroup(s).