git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Pipping <webmaster@hartwork.org>
To: git@vger.kernel.org
Subject: "git cat-file <sha1>" shows usage but should not?
Date: Wed, 15 Apr 2009 18:50:47 +0200	[thread overview]
Message-ID: <49E61067.6060802@hartwork.org> (raw)

Here is what I did:


$ git cat-file -t b8c11fbbffbe171c4960058fa2d96f708e57a80c
commit

$ git cat-file b8c11fbbffbe171c4960058fa2d96f708e57a80c
usage: git cat-file [-t|-s|-e|-p|<type>] <sha1>
   or: git cat-file [--batch|--batch-check] < <list_of_sha1s>
[..]

$ git --version
git version 1.6.3.rc0.1.gf800.dirty



Sebastian

             reply	other threads:[~2009-04-15 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 16:50 Sebastian Pipping [this message]
2009-04-15 16:54 ` "git cat-file <sha1>" shows usage but should not? Jeff King
2009-04-15 16:56   ` Sebastian Pipping
2009-04-15 17:04     ` Jeff King
2009-04-15 17:18       ` Junio C Hamano
2009-04-15 17:34         ` Jeff King
2009-04-15 17:33       ` Julian Phillips
2009-04-15 17:36         ` 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=49E61067.6060802@hartwork.org \
    --to=webmaster@hartwork.org \
    --cc=git@vger.kernel.org \
    /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).