From: Junio C Hamano <gitster@pobox.com>
To: "Øystein Walle" <oystwa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG (maybe)] git rev-parse --verify --quiet isn't quiet
Date: Thu, 04 Sep 2014 11:12:39 -0700 [thread overview]
Message-ID: <xmqqppfbtfu0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq1trruv3b.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Thu, 04 Sep 2014 10:57:44 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I would suspect that this may be fine.
>
> "rev-parse --verify" makes sure the named object exists, but in this
> case @{u} does not even name any object, does it?
Hmph, but "rev-parse --verify no-such-branch" does *not* name any
object, we would want to see it barf, and we probably would want to
be able to squelch the message. So it is unclear if @{u} barfing is
a good idea.
What is the reason why it is inpractical to pass 'quiet' down the
callchain?
next prev parent reply other threads:[~2014-09-04 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 11:20 [BUG (maybe)] git rev-parse --verify --quiet isn't quiet Øystein Walle
2014-09-04 17:57 ` Junio C Hamano
2014-09-04 18:12 ` Junio C Hamano [this message]
2014-09-05 7:15 ` Øystein Walle
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=xmqqppfbtfu0.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=oystwa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.