git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Request: Adding -q/--quiet option to git-cat-file
Date: Sat, 02 Dec 2006 22:32:33 +0100	[thread overview]
Message-ID: <eksr9n$s2c$1@sea.gmane.org> (raw)

The only "committag" gitweb implements now is linking the full 40-char sha
of a commit to a "commit" view. This requires checking the type of object
given by sha1... but git-cat-file -t writes errors to stdout if the object
does not exist. I'd rather not use additional call, using git-cat-file -e,
or using 'string' version of magic "-|" open to redirect stdout to /dev/null
(as it is additional fork anyway).

What I need is an option -q/--quiet to git-cat-file to forbid printing error
messages to stderr... but it looks like it would be easier to add it
universally for all commands, or add it to git wrapper.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


                 reply	other threads:[~2006-12-02 21:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='eksr9n$s2c$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --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).