From: Karel Zak <kzak@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 1/3] Manual pages: runuser.1: Various wording and formatting fixes
Date: Mon, 15 Jun 2020 11:37:33 +0200 [thread overview]
Message-ID: <20200615093733.5hvpjpkrh7paoxd3@ws.net.home> (raw)
In-Reply-To: <20200612111933.3043314-1-mtk.manpages@gmail.com>
On Fri, Jun 12, 2020 at 01:19:31PM +0200, Michael Kerrisk (man-pages) wrote:
> login-utils/runuser.1 | 70 +++++++++++++++++++++----------------------
> 1 file changed, 35 insertions(+), 35 deletions(-)
All 3 patches applied. Thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2020-06-15 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 11:19 [PATCH 1/3] Manual pages: runuser.1: Various wording and formatting fixes Michael Kerrisk (man-pages)
2020-06-12 11:19 ` [PATCH 2/3] Manual pages: setpriv.1: Various minor " Michael Kerrisk (man-pages)
2020-06-12 11:19 ` [PATCH 3/3] Manual pages: setpriv.1: warn users of restrictions on capability changes Michael Kerrisk (man-pages)
2020-06-15 9:37 ` Karel Zak [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=20200615093733.5hvpjpkrh7paoxd3@ws.net.home \
--to=kzak@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).