From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Eric Sandeen <sandeen@redhat.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Uri Corin <uri.corin@gmail.com>
Subject: Re: [PATCH] mke2fs: further updates for mke2fs(8) man page
Date: Tue, 17 Dec 2013 20:52:27 -0500 [thread overview]
Message-ID: <20131218015227.GC19261@thunk.org> (raw)
In-Reply-To: <83B3938A-DEF8-4C05-9511-BA830DCCD692@dilger.ca>
On Tue, Dec 17, 2013 at 03:22:15PM -0700, Andreas Dilger wrote:
>
> Actually, the comments about metadata checksums is commented out in
> the man page. That isn't obvious at first glance. I had just seen
> it in the previous page, and the old description "a superset of the
> uninit_bg feature" wasn't very useful.
It's commented out because the changes are going into the maint
branch, which does not yet have metadata_csum support. Once things
settle down, I'll uncomment the text on the next/master branch, but I
didn't want to do that until we were done editing the man pages, to
avoid merge headaches.
I guess most people aren't as conversant with nroff macros any more
--- it was pretty obvious to me they were commented out. TeX and
LibreOffice has ruined us all. :-)
> As with anything, no complaints about the previous patch - it definitely
> improved the old content, and there is much more that needs to be done
> to document the metadata checksum feature (tune2fs, e2fsck, etc).
Yes, and many thanks Uri for working on improving the documentation.
It's something that has been badly needed for some time.
Cheers,
- Ted
prev parent reply other threads:[~2013-12-18 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 8:17 [PATCH] mke2fs: further updates for mke2fs(8) man page Andreas Dilger
2013-12-17 15:11 ` Eric Sandeen
2013-12-17 22:22 ` Andreas Dilger
2013-12-18 1:52 ` Theodore Ts'o [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=20131218015227.GC19261@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).