From: Rodrigo Campos <rodrigo@sdfg.com.ar>
To: util-linux@vger.kernel.org
Subject: Re: fallocate: Add "--dig-holes" options and minor fixes
Date: Sat, 25 Jan 2014 19:23:03 +0000 [thread overview]
Message-ID: <20140125192303.GA7455@sdfg.com.ar> (raw)
In-Reply-To: <1390677448-7173-1-git-send-email-rodrigo@sdfg.com.ar>
On Sat, Jan 25, 2014 at 07:17:25PM +0000, Rodrigo Campos wrote:
> Hi,
>
> As discussed in this[1] gmane thread, I'm submitting the funtionality to dig
> holes as part of the fallocate(1) command.
Ohh, forgot to tell, but I tried to re-use already used strings in _("")
contructors and make "perror" just print the function name, as that is what I
observed in other util-linux tools.
If I missed something, please let me know :)
Thanks again.
Rodrigo
next prev parent reply other threads:[~2014-01-25 19:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 19:17 fallocate: Add "--dig-holes" options and minor fixes Rodrigo Campos
2014-01-25 19:17 ` [PATCH 1/3] fallocate: Clarify that space can also be deallocated Rodrigo Campos
2014-01-25 19:17 ` [PATCH 2/3] fallocate: Hide #ifdef tricks to call fallocate in a function Rodrigo Campos
2014-01-25 19:17 ` [PATCH 3/3] fallocate: Add "--dig-holes" option Rodrigo Campos
2014-01-26 14:43 ` [PATCH v2] " Rodrigo Campos
2014-01-26 15:06 ` [PATCH v3] " Rodrigo Campos
2014-02-14 10:47 ` Karel Zak
2014-02-14 11:34 ` Karel Zak
2014-02-14 13:16 ` Rodrigo Campos
2014-02-14 13:07 ` Rodrigo Campos
2014-02-14 13:30 ` Karel Zak
2014-02-14 13:35 ` Rodrigo Campos
2014-02-17 10:32 ` Karel Zak
2014-02-17 14:15 ` Rodrigo Campos
2014-02-17 14:49 ` Karel Zak
2014-02-17 15:42 ` Rodrigo Campos
2014-01-25 19:23 ` Rodrigo Campos [this message]
[not found] ` <20140201040414.GA23360@sdfg.com.ar>
2014-02-11 11:31 ` fallocate: Add "--dig-holes" options and minor fixes Rodrigo Campos
2014-02-11 18:34 ` Karel Zak
2014-02-11 18:43 ` Rodrigo Campos
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=20140125192303.GA7455@sdfg.com.ar \
--to=rodrigo@sdfg.com.ar \
--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