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

[RFC/PATCH 0/2] status -s: Use the same config as status

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Nov 26, 2009, 15:24 UTC
Message-ID
<cover.1259248243.git.git@drmicha.warpmail.net>

This mini series is an RFC for bringing the short version of status in line with the longer one. They already both obey status.showUntrackedFiles. Currently, status -s does not obey status.relativePaths nor color.status.

I think status should follow the priniciple of least surprise here in the sense that -s should not change other aspects of the output (although it is very different internally).

I think we don't have any tests for status -s yet, which is one reason why this is an RFC: I don't expect to get through with it, like the introducer of status -s did ;) Another reason is mentioned in 2/2.

Michael J Gruber (2):
  status -s: respect the status.relativePaths option
  status -s: obey color.status
 builtin-commit.c |   22 +++++++++++++++++-----
 wt-status.c      |    2 +-
 wt-status.h      |    1 +
 3 files changed, 19 insertions(+), 6 deletions(-)
Next: Michael J Gruber
Message 1 of 14 in “status -s: Use the same config as status”
  1. 0/2 status -s: Use the same config as statusMichael J Gruber, Nov 26, 2009
  2. 1/2 status -s: respect the status.relativePaths optionMichael J Gruber, Nov 26, 2009
  3. Junio C HamanoNov 27, 2009
  4. Jeff KingNov 27, 2009
  5. 2/2 status -s: obey color.statusMichael J Gruber, Nov 26, 2009
  6. Johannes SixtNov 26, 2009
  7. Michael J GruberNov 26, 2009
  8. Junio C HamanoNov 26, 2009
  9. Add a notice that only certain functions can print color escape codesJohannes Sixt, Nov 27, 2009
  10. Junio C HamanoNov 27, 2009
  11. Johannes SixtNov 27, 2009
  12. Michael J GruberNov 27, 2009
  13. Junio C HamanoNov 27, 2009
  14. Michael J GruberNov 27, 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.