All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>
Subject: [PATCH] Changed type field to be %x for tree header (line in btrfs_print_tree)
Date: Tue, 10 Jun 2008 11:46:50 -0400	[thread overview]
Message-ID: <484EA1EA.7000006@hp.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2: 0001-Changed-type-field-to-be-x-for-tree-header-like-in.patch --]
[-- Type: text/x-diff, Size: 758 bytes --]

This makes it easier to visually match keys - see:
print-tree.c:btrfs_print_tree():329:

	printf("\tkey %d (%llu %x %llu) block %llu (%llu) gen %llu\n",

I'm not sure if this breaks any other parsers?

Signed-off-by: Alan D. Brunelle <alan.brunelle@hp.com>
---
 debug-tree.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/debug-tree.c b/debug-tree.c
index fa5c90c..9185dc2 100644
--- a/debug-tree.c
+++ b/debug-tree.c
@@ -190,7 +190,7 @@ int main(int ac, char **av)
 				break;
 			}
 			if (!skip && !extent_only) {
-				printf("tree %llu %u %llu\n",
+				printf("tree %llu %x %llu\n",
 				       (unsigned long long)found_key.objectid,
 				       found_key.type,
 				       (unsigned long long)found_key.offset);
-- 
1.5.4.3


             reply	other threads:[~2008-06-10 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 15:46 Alan D. Brunelle [this message]
2008-06-10 18:30 ` [PATCH] Changed type field to be %x for tree header (line in btrfs_print_tree) Chris Mason
2008-06-10 19:01   ` Alan D. Brunelle

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=484EA1EA.7000006@hp.com \
    --to=alan.brunelle@hp.com \
    --cc=chris.mason@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.