From: Peter Cordes <peter@cordes.ca>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] fallocate: create mode 0666, that's what umask is for
Date: Thu, 08 Jan 2015 14:26:35 -0400 [thread overview]
Message-ID: <20150108182635.GV29504@cordes.ca> (raw)
In-Reply-To: <20150108091302.GI15715@x2.net.home>
On Thu, Jan 08, 2015 at 10:13:02AM +0100, Karel Zak wrote:
> 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.
Sure, no rush. Agree it's not something that's ready to go in for a
release you're already finalizing.
I only just subscribed to the mailing list to post my patches.
Thanks for the heads up on release-schedule issues, so I can stop
worrying that you missed it or something. :)
If anyone has any thoughts about the design, esp. from the point of
view of a different use-case for --dig-holes (like maybe for VM
images?), that would be useful. I could maybe revise my patch and
have something closer to ready for inclusion into 2.27.
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@cor , des.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BC
prev parent reply other threads:[~2015-01-08 18:26 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
2015-01-08 18:26 ` Peter Cordes [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=20150108182635.GV29504@cordes.ca \
--to=peter@cordes.ca \
--cc=kzak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.