Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-show vs. btrfs different output
Date: 21 Mar 2013 16:35:00 +0100	[thread overview]
Message-ID: <CTGgK889CXB@helmut.hullen.de> (raw)
In-Reply-To: <CAKuK5J05iXaDd7Q4fLby9vJyPXBURx06xb0_--WmgTpJ0j2RoA@mail.gmail.com>

Hallo, Jon,

Du meintest am 21.03.13:

> First btrfs-show (git):

> **
> ** WARNING: this program is considered deprecated
> ** Please consider to switch to the btrfs utility

"btrfs-show" makes nasty errors, especially together with "blkid".  
Delete "btrfs-show". That's the safe way.

Viele Gruesse!
Helmut

      parent reply	other threads:[~2013-03-21 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 15:04 btrfs-show vs. btrfs different output Jon Nelson
2013-03-21 15:11 ` Eric Sandeen
2013-03-21 15:29   ` Jon Nelson
2013-03-21 15:33     ` Helmut Hullen
2013-03-21 16:25     ` Eric Sandeen
2013-03-22  3:06       ` Anand Jain
2013-03-22 13:59       ` Jon Nelson
2013-03-22 22:34         ` Eric Sandeen
2013-03-21 15:35 ` Helmut Hullen [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=CTGgK889CXB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --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