From: Junio C Hamano <gitster@pobox.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH] Produce a nicer output in case of sha1_object_info failures in ls-tree -l
Date: Thu, 19 Mar 2009 16:08:43 -0700 [thread overview]
Message-ID: <7v4oxp6rgk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090319225429.GC8433@blimp.localdomain> (Alex Riesen's message of "Thu, 19 Mar 2009 23:54:29 +0100")
Alex Riesen <raa.lkml@gmail.com> writes:
> How about this patch instead? I chose "BAD" for the marker, as any
> automatic processing trying blindly to convert it into a number will
> get a 0, which seems safe to me.
Such a broken automatic processing won't mind getting any garbage; the
choice among this patch, your original "say 0 when we do not know" patch,
or unpatched "size is undefined when an entry is corrupt" git wouldn't
make a whit of difference to it.
An automatic processing that does validate its input will notice BAD is
not a number, and can handle such a corrupt entry more sanely, which is
potentially a big plus.
I think this round is a big improvement.
> builtin-ls-tree.c | 22 ++++++++++++----------
> 1 files changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/builtin-ls-tree.c b/builtin-ls-tree.c
> index fca4631..22008df 100644
> --- a/builtin-ls-tree.c
> +++ b/builtin-ls-tree.c
> @@ -60,7 +60,6 @@ static int show_tree(const unsigned char *sha1, const char *base, int baselen,
> {
> int retval = 0;
> const char *type = blob_type;
> - unsigned long size;
>
> if (S_ISGITLINK(mode)) {
> /*
> @@ -90,17 +89,20 @@ static int show_tree(const unsigned char *sha1, const char *base, int baselen,
>
> if (!(ls_options & LS_NAME_ONLY)) {
> if (ls_options & LS_SHOW_SIZE) {
> + char size_text[24];
> if (!strcmp(type, blob_type)) {
> - sha1_object_info(sha1, &size);
> - printf("%06o %s %s %7lu\t", mode, type,
> - abbrev ? find_unique_abbrev(sha1, abbrev)
> - : sha1_to_hex(sha1),
> - size);
> + unsigned long size;
> + if (sha1_object_info(sha1, &size) == OBJ_BAD)
> + strcpy(size_text, "BAD");
> + else
> + snprintf(size_text, sizeof(size_text),
> + "%lu", size);
> } else
> - printf("%06o %s %s %7c\t", mode, type,
> - abbrev ? find_unique_abbrev(sha1, abbrev)
> - : sha1_to_hex(sha1),
> - '-');
> + strcpy(size_text, "-");
> + printf("%06o %s %s %7s\t", mode, type,
> + abbrev ? find_unique_abbrev(sha1, abbrev)
> + : sha1_to_hex(sha1),
> + size_text);
> } else
> printf("%06o %s %s\t", mode, type,
> abbrev ? find_unique_abbrev(sha1, abbrev)
> --
> 1.6.2.1.237.g7206c6
prev parent reply other threads:[~2009-03-19 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 20:30 [PATCH] Produce a nicer output in case of sha1_object_info failures in ls-tree -l Alex Riesen
2009-03-19 21:55 ` Junio C Hamano
2009-03-19 22:00 ` Alex Riesen
2009-03-19 22:13 ` Junio C Hamano
2009-03-19 22:54 ` Alex Riesen
2009-03-19 23:08 ` Junio C Hamano [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=7v4oxp6rgk.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=raa.lkml@gmail.com \
/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.