From: Sebastian Pipping <webmaster@hartwork.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: "git cat-file <sha1>" shows usage but should not?
Date: Wed, 15 Apr 2009 18:56:05 +0200 [thread overview]
Message-ID: <49E611A5.8090602@hartwork.org> (raw)
In-Reply-To: <20090415165420.GB24528@coredump.intra.peff.net>
Jeff King wrote:
> That usage message is misleading. You need to use one of -t, -s, -e, -p,
> or <type>. So it should perhaps just be:
>
> git cat-file -t|-s|-e|-p|<type> <sha1>
>
> though that looks terribly ugly. Suggestions welcome.
Thanks for making that clear. How about round or curly brackets?
Sebastian
next prev parent reply other threads:[~2009-04-15 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 16:50 "git cat-file <sha1>" shows usage but should not? Sebastian Pipping
2009-04-15 16:54 ` Jeff King
2009-04-15 16:56 ` Sebastian Pipping [this message]
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=49E611A5.8090602@hartwork.org \
--to=webmaster@hartwork.org \
--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).