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

Re: [PATCH] rebase: consistent error messages for staged and unstaged changes.

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Aug 6, 2009, 09:56 UTC
Message-ID
<vpqljlx465w.fsf@bauges.imag.fr>
In-Reply-To
<7vws5i9nsy.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 6 quoted lines
> Matthieu Moy <Matthieu.Moy@imag.fr> writes:
>
>> Previous version expose the output of the plumbing update-index to the
>> user, which novice users have difficulty to understand.
>
> Can't -q(uiet) option of update-index be used for this?
No, since update-index -q doesn't set the exit status properly:

$ git update-index --ignore-submodules --refresh > /dev/null; echo $? 1 $ git update-index --ignore-submodules -q --refresh ; echo $? 0

-- 
Matthieu
Previous: Junio C Hamano
Message 3 of 3 in “rebase: consistent error messages for staged and unstaged changes.”
  1. rebase: consistent error messages for staged and unstaged changes.Matthieu Moy, Aug 5, 2009
  2. Junio C HamanoAug 5, 2009
  3. Matthieu MoyAug 6, 2009

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.