From: Adrian Reber <areber@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH 2/2] clone.2: added clone3() set_tid information
Date: Mon, 2 Dec 2019 15:25:35 +0100 [thread overview]
Message-ID: <20191202142535.GC34164@dcbz.redhat.com> (raw)
In-Reply-To: <49be41bf-f6e5-c0ea-e6fb-22eeea9656e8@gmail.com>
Christian and Michael,
thanks for the reviews. I tried to apply all suggested changes in v2
which I will send out in a few minutes.
Adrian
next prev parent reply other threads:[~2019-12-02 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 12:46 [PATCH 1/2] clone.2: tfix Adrian Reber
2019-11-28 12:46 ` [PATCH 2/2] clone.2: added clone3() set_tid information Adrian Reber
2019-11-28 17:24 ` Christian Brauner
2019-11-29 13:56 ` Adrian Reber
2019-12-01 12:17 ` Michael Kerrisk (man-pages)
2019-12-01 12:18 ` Michael Kerrisk (man-pages)
2019-12-02 14:25 ` Adrian Reber [this message]
2019-12-01 12:18 ` Michael Kerrisk (man-pages)
2019-11-28 13:30 ` [PATCH 1/2] clone.2: tfix Christian Brauner
2019-12-01 12:16 ` Michael Kerrisk (man-pages)
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=20191202142535.GC34164@dcbz.redhat.com \
--to=areber@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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).