From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 1/1] bash-completion: release preparations
Date: Mon, 15 Jun 2020 11:38:58 +0200 [thread overview]
Message-ID: <20200615093858.32jioy4dlfdchwns@ws.net.home> (raw)
In-Reply-To: <20200612192954.2965-1-kerolasa@iki.fi>
On Fri, Jun 12, 2020 at 08:29:54PM +0100, Sami Kerola wrote:
> bash-completion/blkdiscard | 1 +
> bash-completion/blkzone | 2 +-
> bash-completion/cfdisk | 1 +
> bash-completion/fdisk | 3 +++
> bash-completion/lsirq | 1 +
> bash-completion/mkswap | 2 +-
> bash-completion/nsenter | 1 +
> bash-completion/sfdisk | 3 +++
> bash-completion/wipefs | 1 +
> 9 files changed, 13 insertions(+), 2 deletions(-)
Applied, thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2020-06-15 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 19:29 [PATCH 1/1] bash-completion: release preparations Sami Kerola
2020-06-15 9:38 ` 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=20200615093858.32jioy4dlfdchwns@ws.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@iki.fi \
--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).