All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dave@jikos.cz>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: dave@jikos.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs + Btrfs-progs:  make pipe functions re-usable
Date: Thu, 20 Sep 2012 14:34:19 +0200	[thread overview]
Message-ID: <20120920123419.GL17430@twin.jikos.cz> (raw)
In-Reply-To: <505807A9.8060401@oracle.com>

On Tue, Sep 18, 2012 at 01:33:29PM +0800, Anand Jain wrote:
>   '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.

Is it modelled after ZFS 'zpool history' command? AFAICS it captures
actions modifiying the pools, there's nothing similar for btrfs.

david

      reply	other threads:[~2012-09-20 12:34 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
2012-09-20 12:34         ` 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=20120920123419.GL17430@twin.jikos.cz \
    --to=dave@jikos.cz \
    --cc=Anand.Jain@oracle.com \
    --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 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.