From: Andrew Burgess <aab@cichlid.com>
To: Uri Corin <uri.corin@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsprogs: dumpe2fs manpage updates
Date: Tue, 17 Dec 2013 07:14:34 -0800 [thread overview]
Message-ID: <1387293274.17633.2@hogo> (raw)
In-Reply-To: <CAO+X6Oiq5PLxjcGkjNi=D3qr=hB_zaCkgQfNcNjBQJaVjsNKBQ@mail.gmail.com> (from uri.corin@gmail.com on Tue Dec 17 06:49:49 2013)
On 12/17/2013 06:49:49 AM, Uri Corin wrote:
> +.TP
> +.B extra_isize
> +.br
> +This feature enables storage of nanosecond timestamps and creation
> +time, if the inode size is larger than 256 bytes or larger.
this should either say "256 bytes or larger" or "larger than 256 bytes"
(i'm not sure which is true)
next prev parent reply other threads:[~2013-12-17 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 14:49 [PATCH] e2fsprogs: dumpe2fs manpage updates Uri Corin
2013-12-17 15:14 ` Andrew Burgess [this message]
2013-12-17 22:46 ` Andreas Dilger
2013-12-24 19:20 ` Theodore Ts'o
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=1387293274.17633.2@hogo \
--to=aab@cichlid.com \
--cc=linux-ext4@vger.kernel.org \
--cc=uri.corin@gmail.com \
/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