From: Paul Mackerras <paulus@samba.org>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: git command to read
Date: Tue, 21 Oct 2008 22:45:28 +1100 [thread overview]
Message-ID: <18685.49368.557513.727997@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20081021112521.GC17363@coredump.intra.peff.net>
Jeff King writes:
> On Tue, Oct 21, 2008 at 10:21:09PM +1100, Paul Mackerras wrote:
>
> > Is there a command in git at the moment that will read commit IDs on
> > standard input and print the contents of each commit on standard
> > output (without waiting for EOF on stdin)?
>
> How about:
>
> git cat-file --batch
>
> ?
>
> Unfortunately it just dumps the raw commit information instead of
> allowing the usual formatting, but perhaps that is sufficient (you asked
> for "contents").
Ah, thank you, that looks like just what I want. :)
Paul.
next prev parent reply other threads:[~2008-10-21 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 11:21 git command to read Paul Mackerras
2008-10-21 11:25 ` Jeff King
2008-10-21 11:45 ` Paul Mackerras [this message]
2008-10-21 12:06 ` Alexander Gavrilov
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=18685.49368.557513.727997@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).