All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [PATCH v3 1/8] Btrfs-progs: add missing man page information for btrfsck
Date: Fri, 30 Aug 2013 17:58:21 +0200	[thread overview]
Message-ID: <20130830155821.GM23113@twin.jikos.cz> (raw)
In-Reply-To: <1376454557-3041-1-git-send-email-wangsl.fnst@cn.fujitsu.com>

On Wed, Aug 14, 2013 at 12:29:10PM +0800, Wang Shilong wrote:
> Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
> ---
> v2->v3: availiable parts is not true anymore,remove it.
> v1->v2: remove wrong copyrights.

Thanks for the updates, I've put the series into integration.

Note for future:

The manpages document the current state, ie. there are numerous separate
utilities which we would like to move under the main tool. When it
happens the man contents shall be moved as well.

david

      parent reply	other threads:[~2013-08-30 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14  4:29 [PATCH v3 1/8] Btrfs-progs: add missing man page information for btrfsck Wang Shilong
2013-08-14  4:29 ` [PATCH v3 2/8] Btrfs-progs: add missing man information for btrfs-debug-tree Wang Shilong
2013-08-14  4:29 ` [PATCH v3 3/8] Btrfs-progs: add missing man page for btrfs-show-super Wang Shilong
2013-08-14  4:29 ` [PATCH v3 4/8] Btrfs-progs: add man page information for btrfs-find-root Wang Shilong
2013-08-14  4:29 ` [PATCH v3 5/8] Btrfs-progs: add man page information for btrfs-convert Wang Shilong
2013-08-14  4:29 ` [PATCH v3 6/8] Btrfs-progs: add missing man page for btrfstune Wang Shilong
2013-08-14  4:29 ` [PATCH v3 7/8] Btrfs-progs: add missing man page information for btrfs-zero-log Wang Shilong
2013-08-14  4:29 ` [PATCH v3 8/8] Btrfs-progs: add missing man page for btrfs-map-logical Wang Shilong
2013-08-30 15:58 ` David Sterba [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=20130830155821.GM23113@twin.jikos.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.