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

Re: [PATCH] Added --exit-code option to git-status

From
Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Date
Mar 5, 2011, 16:32 UTC
Message-ID
<AANLkTimeE0yscLFTkJ-824wi55eQQme8X+qobx80NVby@mail.gmail.com>
In-Reply-To
<7v4o7h5z1i.fsf@alter.siamese.dyndns.org>
On Sat, Mar 5, 2011 at 5:10 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:
>
>> When this option is specified git-status returns non-zero
>> exit code when there are untracked, modifed or staged files.
>> ...
>> Comments?
>
> Knowing the history of "commit --dry-run" vs "status", my gut reaction was
> that adding anything to "status" is going totally backwards.
What's the history?
-- 
Piotrek
Previous: Junio C Hamano
Message 3 of 3 in “Added --exit-code option to git-status”
  1. Added --exit-code option to git-statusPiotr Krukowiecki, Mar 5, 2011
  2. Junio C HamanoMar 5, 2011
  3. Piotr KrukowieckiMar 5, 2011

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.