From: Karel Zak <kzak@redhat.com>
To: Andrew Price <anprice@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] fallocate.1: List gfs2 as supporting punch-hole
Date: Fri, 8 Nov 2019 11:18:46 +0100 [thread overview]
Message-ID: <20191108101846.lbhr6gzwescn2yrz@10.255.255.10> (raw)
In-Reply-To: <20191031165144.1877-1-anprice@redhat.com>
On Thu, Oct 31, 2019 at 04:51:44PM +0000, Andrew Price wrote:
> sys-utils/fallocate.1 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2019-11-08 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 16:51 [PATCH] fallocate.1: List gfs2 as supporting punch-hole Andrew Price
2019-11-08 10:18 ` 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=20191108101846.lbhr6gzwescn2yrz@10.255.255.10 \
--to=kzak@redhat.com \
--cc=anprice@redhat.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).