From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Alan Mackenzie <acm@muc.de>, git@vger.kernel.org
Subject: Re: How do I get the file contents from an arbitrary revision to stdout?
Date: Fri, 08 Oct 2021 14:54:51 -0700 [thread overview]
Message-ID: <xmqqtuhri3mc.fsf@gitster.g> (raw)
In-Reply-To: <YWCj6NqMrxksN1V8@coredump.intra.peff.net> (Jeff King's message of "Fri, 8 Oct 2021 16:02:48 -0400")
Jeff King <peff@peff.net> writes:
> git cat-file -p bar-branch:foo.c
>
> (the "-p" is "pretty-print based on the object's type", so the two are
> equivalent).
IIRC, "cat-file -p" doesn't do textconv, but "show" would, and
depending on the use case the difference may matter.
next prev parent reply other threads:[~2021-10-08 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 17:51 How do I get the file contents from an arbitrary revision to stdout? Alan Mackenzie
2021-10-08 18:01 ` Konstantin Ryabitsev
2021-10-08 18:15 ` Alan Mackenzie
2021-10-08 20:02 ` Jeff King
2021-10-08 21:54 ` Junio C Hamano [this message]
2021-10-08 23:01 ` Jeff King
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=xmqqtuhri3mc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=acm@muc.de \
--cc=git@vger.kernel.org \
--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).