From: Mimi Zohar <zohar@linux.ibm.com>
To: David Howells <dhowells@redhat.com>, Denis Kenzior <denkenz@gmail.com>
Cc: keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
mtk.manpages@gmail.com
Subject: Re: [KEYUTILS PATCH] Add manpages for asymmetric key type and ops
Date: Wed, 07 Nov 2018 10:08:01 -0500 [thread overview]
Message-ID: <1541603281.3928.2.camel@linux.ibm.com> (raw)
In-Reply-To: <13898.1541601730@warthog.procyon.org.uk>
On Wed, 2018-11-07 at 14:42 +0000, David Howells wrote:
> Add man pages for asymmetric key type and ops
>
> Add manual pages for the asymmetric key type and its specialised keyctl
> operations.
After cloning the man pages*, I'm having troubles applying this patch.
Any suggestions?
Mimi
*https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
next prev parent reply other threads:[~2018-11-07 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 14:42 [KEYUTILS PATCH] Add manpages for asymmetric key type and ops David Howells
2018-11-07 15:08 ` Mimi Zohar [this message]
2018-11-07 16:44 ` David Howells
2018-11-07 16:45 ` David Howells
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=1541603281.3928.2.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=denkenz@gmail.com \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-security-module@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).