From: David Sterba <dsterba@suse.cz>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [v2 2/8] Btrfs-progs: add missing man information for btrfs-debug-tree
Date: Fri, 9 Aug 2013 00:57:57 +0200 [thread overview]
Message-ID: <20130808225756.GF5284@suse.cz> (raw)
In-Reply-To: <1375854849-15224-2-git-send-email-wangsl.fnst@cn.fujitsu.com>
Thanks for updating the license. One comment that's applicable to all
patches:
On Wed, Aug 07, 2013 at 01:54:03PM +0800, Wang Shilong wrote:
> +.SH AVAILABILITY
> +.B btrfs-debug-tree
> +is part of btrfs-progs. Btrfs is currently under heavy development,
> +and not suitable for any uses other than benchmarking and review.
That's (arguably) not true anymore and I'd rather see it removed or
updated closer to current status.
> +Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
> +further details.
next prev parent reply other threads:[~2013-08-08 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 5:54 [v2 1/8] Btrfs-progs: add missing man page information for btrfsck Wang Shilong
2013-08-07 5:54 ` [v2 2/8] Btrfs-progs: add missing man information for btrfs-debug-tree Wang Shilong
2013-08-08 22:57 ` David Sterba [this message]
2013-08-07 5:54 ` [v2 3/8] Btrfs-progs: add missing man page for btrfs-show-super Wang Shilong
2013-08-07 5:54 ` [v2 4/8] Btrfs-progs: add man page information for btrfs-find-root Wang Shilong
2013-08-07 6:46 ` Stefan Behrens
2013-08-07 8:35 ` Wang Shilong
2013-08-07 5:54 ` [v2 5/8] Btrfs-progs: add man page information for btrfs-convert Wang Shilong
2013-08-07 5:54 ` [v2 6/8] Btrfs-progs: add missing man page for btrfstune Wang Shilong
2013-08-07 5:54 ` [v2 7/8] Btrfs-progs: add missing man page information for btrfs-zero-log Wang Shilong
2013-08-07 5:54 ` [v2 8/8] Btrfs-progs: add missing man page for btrfs-map-logical Wang Shilong
2013-08-07 8:30 ` [patch v2 resend 4/8] Btrfs-progs: add man page information for btrfs-find-root Wang Shilong
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=20130808225756.GF5284@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangsl.fnst@cn.fujitsu.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.