From: Junio C Hamano <junkio@cox.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] A few more options for git-cat-file
Date: Sat, 03 Dec 2005 22:17:28 -0800 [thread overview]
Message-ID: <7vu0dptmh3.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 43924D1C.8070306@zytor.com
"H. Peter Anvin" <hpa@zytor.com> writes:
> This adds the following options to git-cat-file:
>
> -n, to get the canonical name of a resource. This is for one thing
> useful in tagging scripts.
Isn't "git-rev-parse --verify" good enough?
> -e, to test for the existence of a file.
This might be useful and cleaner than "cat-file -s >/dev/null"
but marginally so. While reading the whole file and discarding
that to /dev/null is wasteful and would go against tastes of
many people, -t and -s flags do not need to read the whole thing
and not so expensive.
next prev parent reply other threads:[~2005-12-04 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 1:57 [PATCH] A few more options for git-cat-file H. Peter Anvin
2005-12-04 6:17 ` Junio C Hamano [this message]
2005-12-04 6:22 ` H. Peter Anvin
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=7vu0dptmh3.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
/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).