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

Git Status Short Output Color Inconsistency with -z Flag

From
LLangbart <langbart@protonmail.com>
Date
Oct 5, 2025, 00:48 UTC
Message-ID
<XCDlwEkTlgoZIyIf_8BfOGl1C3C63Ioxeib4BRNJ9Jm_CtYWKT3qu-pDaeXVtS1Ifq6E4pT9G0yDbIS_nSwN-uiBuBNAlMyrOv0R1RyM7oc=@protonmail.com>
What did you do before the bug happened? (Steps to reproduce your issue)
1. Create an untracked file and modify an existing tracked file
2. Run: git status --short -z
What did you expect to happen? (Expected behavior)
All status markers have colors disabled
What happened instead? (Actual behavior)
- Modified marker (`M`) appears colored
- Untracked marker (`??`) appears *uncolored*
Related patch:
https://lore.kernel.org/git/cover.1260025135.git.git@drmicha.warpmail.net/T/#u
git version 2.51.0
Next: Jeff King
Message 1 of 7 in “Git Status Short Output Color Inconsistency with -z Flag”
  1. LangbartOct 5, 2025
  2. Jeff KingOct 7, 2025
  3. status: make coloring of "-z --short" consistentJeff King, Oct 7, 2025
  4. status: make coloring of "-z --short" consistentJeff King, Oct 17, 2025
  5. LangbartOct 18, 2025
  6. Jeff KingOct 18, 2025
  7. LangbartOct 18, 2025

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.