From: Theodore Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: debugfs: document zap_block & dump_block
Date: Sat, 12 Jan 2013 17:22:21 -0500 [thread overview]
Message-ID: <20130112222221.GA31368@thunk.org> (raw)
In-Reply-To: <50F04E89.7070501@redhat.com>
On Fri, Jan 11, 2013 at 07:40:25AM -0000, Eric Sandeen wrote:
> What little docs there were had a cut & paste error.
> We can do better. :)
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Applied, thanks for improving the documentation!
- Ted
prev parent reply other threads:[~2013-01-12 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 17:40 [PATCH] debugfs: document zap_block & dump_block Eric Sandeen
2013-01-12 22:22 ` 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=20130112222221.GA31368@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 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.