linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: dave@jikos.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs + Btrfs-progs:  make pipe functions re-usable
Date: Tue, 18 Sep 2012 13:33:29 +0800	[thread overview]
Message-ID: <505807A9.8060401@oracle.com> (raw)
In-Reply-To: <20120917145957.GQ17430@twin.jikos.cz>


>>> What's 'service sub-cmd' please?
>>
>>    at the moment 'btrfs service history<mnt>|<dev>'
>>    to show logs of maintenance.
>>    comments/suggestions welcome.
>
> Sorry, but without a more detailed description I can hardly give useful
> comments.


David,

   'btrfs service history <mnt>|<dev>'
  is basically to show the list of cli/gui commands which are
  successfully run on the btrfs as part of its -
  creation (may be), configuration and maintenance.

  HTH.

Thanks, Anand


  reply	other threads:[~2012-09-18  5:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  5:50 [PATCH] Btrfs + Btrfs-progs: make pipe functions re-usable anand jain
2012-09-14  6:04 ` [PATCH] Btrfs-progs: make dump_thread and write_buf usable outside cmds-send.c Anand jain
2012-09-14  6:04   ` [PATCH] Btrfs-progs: making send.h inline with its kernel side change Anand jain
2012-09-14  6:04   ` [PATCH] Btrfs: write_buf is now callable outside send.c Anand jain
2012-09-14 11:04 ` [PATCH] Btrfs + Btrfs-progs: make pipe functions re-usable David Sterba
2012-09-17  4:48   ` Anand Jain
2012-09-17 10:28     ` Hugo Mills
2012-09-18  3:39       ` Anand Jain
2012-09-17 14:59     ` David Sterba
2012-09-18  5:33       ` Anand Jain [this message]
2012-09-20 12:34         ` David Sterba

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=505807A9.8060401@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dave@jikos.cz \
    --cc=linux-btrfs@vger.kernel.org \
    /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).