git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG (maybe)] git rev-parse --verify --quiet isn't quiet

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 4, 2014, 18:12 UTC
Message-ID
<xmqqppfbtfu0.fsf@gitster.dls.corp.google.com>
In-Reply-To
<xmqq1trruv3b.fsf@gitster.dls.corp.google.com>
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?

Previous: Junio C HamanoNext: Øystein Walle
Message 3 of 4 in “[BUG (maybe)] git rev-parse --verify --quiet isn't quiet”
  1. Øystein WalleSep 4, 2014
  2. Junio C HamanoSep 4, 2014
  3. Junio C HamanoSep 4, 2014
  4. Øystein WalleSep 5, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.