From: Junio C Hamano <gitster@pobox•com>
To: Ed Avis <eda@waniasset•com>
Cc: git@vger•kernel.org
Subject: Re: 'git show' with multiple revisions
Date: Wed, 29 Apr 2015 09:08:14 -0700 [thread overview]
Message-ID: <xmqqpp6m6hox.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <loom.20150429T175626-211@post.gmane.org> (Ed Avis's message of "Wed, 29 Apr 2015 16:01:41 +0000 (UTC)")
Ed Avis <eda@waniasset•com> writes:
> Junio C Hamano <gitster <at> pobox.com> writes:
>
>>"cat-file --batch" will give you the objects in the order you ask.
>
> Thanks, that makes it easy to deal with. In fact, I might prefer to use
> git cat-file --batch-check and then use some other library to fetch the blob
> contents.
If all you need is a translation from extended SHA-1 object name
like HEAD~243:Documentation/README to the raw 40-hex object name,
"rev-parse" may turn out to be more suitable tool than that.
It of course depends on your use case.
prev parent reply other threads:[~2015-04-29 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 10:10 'git show' with multiple revisions Ed Avis
2015-04-29 2:04 ` Jeff King
2015-04-29 15:47 ` Ed Avis
2015-04-29 15:53 ` Jeff King
2015-04-29 15:53 ` Junio C Hamano
2015-04-29 16:01 ` Ed Avis
2015-04-29 16: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=xmqqpp6m6hox.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=eda@waniasset$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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