From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>, ZheNing Hu <adlternative@gmail.com>
Cc: ZheNing Hu via GitGitGadget <gitgitgadget@gmail.com>,
Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Christian Couder <christian.couder@gmail.com>,
Hariom Verma <hariom18599@gmail.com>
Subject: Re: [PATCH] [GSOC] cat-file: fix --batch report changed-type bug
Date: Mon, 31 May 2021 11:07:26 -0500 [thread overview]
Message-ID: <60b509be97423_24d2820856@natae.notmuch> (raw)
In-Reply-To: <YLT2UfCZyQIXWIOv@coredump.intra.peff.net>
Jeff King wrote:
> The simplest test is just:
>
> git -C all-two cat-file --batch-all-objects --batch="%(objectname)" >/dev/null
>
> which will currently fail. It would be nice to verify that its output is
> sensible, but I'm not sure how to easily do that (it will spew a bunch
> of binary tree data, and it cannot even be parsed reliably since we
> haven't output the sizes).
I use ruby to parse binary data from git all the time:
git log --format='%b%x00' |
ruby -e 'ARGF.each("\0", chomp: true) { |chunk| p chunk }'
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-31 17:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 8:29 [PATCH] [GSOC] cat-file: fix --batch report changed-type bug ZheNing Hu via GitGitGadget
2021-05-30 21:09 ` Jeff King
2021-05-31 13:20 ` ZheNing Hu
2021-05-31 14:44 ` Jeff King
2021-05-31 15:32 ` ZheNing Hu
2021-05-31 16:07 ` Felipe Contreras [this message]
2021-06-01 1:49 ` Jeff King
2021-06-01 6:34 ` Felipe Contreras
2021-06-01 15:34 ` Jeff King
2021-06-01 16:42 ` Felipe Contreras
2021-06-01 12:46 ` ZheNing Hu
2021-05-30 21:15 ` Junio C Hamano
2021-05-30 21:36 ` Jeff King
2021-06-01 1:40 ` Junio C Hamano
2021-05-31 13:55 ` ZheNing Hu
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=60b509be97423_24d2820856@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=adlternative@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=hariom18599@gmail.com \
--cc=peff@peff.net \
/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).