From: Karel Zak <kzak@redhat.com>
To: Peter Cordes <peter@cordes.ca>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] fallocate: create mode 0666, that's what umask is for
Date: Thu, 8 Jan 2015 10:13:02 +0100 [thread overview]
Message-ID: <20150108091302.GI15715@x2.net.home> (raw)
In-Reply-To: <20150107224626.GS29504@cordes.ca>
On Wed, Jan 07, 2015 at 06:46:26PM -0400, Peter Cordes wrote:
> Thanks for taking a look at my patches. I haven't had any new ideas
> for my fallocate --dig-holes patch. My local copy does what I want it
I didn't look at your second patch yet. I'd like to finalize stuff for
v2.26-rc1 and it seems that with some invasive and large changes we
can wait for v2.27.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-01-08 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 5:02 [PATCH] fallocate: create mode 0666, that's what umask is for Peter Cordes
2015-01-07 9:03 ` Karel Zak
2015-01-07 22:46 ` Peter Cordes
2015-01-08 9:13 ` Karel Zak [this message]
2015-01-08 18:26 ` Peter Cordes
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=20150108091302.GI15715@x2.net.home \
--to=kzak@redhat.com \
--cc=peter@cordes.ca \
--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).