From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: fdmanana@gmail.com
Cc: "dsterba@suse.cz" <dsterba@suse.cz>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] delete obsolete function btrfs_print_tree()
Date: Mon, 4 Apr 2016 18:20:53 +0200 [thread overview]
Message-ID: <57029465.7020904@googlemail.com> (raw)
In-Reply-To: <CAL3q7H5XDU2sNEVmYYsc7L72zCbN7Dpdx-nsSETwdJQd529z0A@mail.gmail.com>
On 04/04/16 18:02, Filipe Manana wrote:
> I use this function frequently during development, and there's a good
> reason to use it instead of the user space tool btrfs-debug-tree.
Good to know, that's why I asked. Printing unwritten extents makes sense.
-h
next prev parent reply other threads:[~2016-04-04 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 14:53 [PATCH] delete obsolete function btrfs_print_tree() Holger Hoffstätte
2016-04-04 13:56 ` David Sterba
2016-04-04 15:54 ` Holger Hoffstätte
2016-04-04 16:02 ` Filipe Manana
2016-04-04 16:20 ` Holger Hoffstätte [this message]
2016-04-04 20:10 ` Dan Carpenter
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=57029465.7020904@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=clm@fb.com \
--cc=dan.carpenter@oracle.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@gmail.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 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).