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

[RFC PATCH 0/1] status: Allow for short-form output by default

From
Thomas Adam <thomas@xteddy.org>
Date
Nov 11, 2012, 22:53 UTC
Message-ID
<1352674383-23654-1-git-send-email-thomas@xteddy.org>
Hi,

It was asked recently whether git status could output the short-form instead of the long output (via its "-sb" options). To that end, I've created a rough POC on how this might look. It's deliberately lacking documentation; I was curious to know whether:

status.shortwithbranch = true

Was going to cut it. Likewise, I was unsure if instead there should be two separate options, one for just short (i.e. '-s') also?

What do others think?

ISTR reading on this list recently the addition of a "--long" option to git status? I'm wondering how this would relate to that, if at all?

Kindly,
Thomas Adam (1):
  status: Allow for short-form via config option
 builtin/commit.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)
-- 
1.7.11.4
Next: Thomas Adam
Message 1 of 3 in “status: Allow for short-form output by default”
  1. 0/1 status: Allow for short-form output by defaultThomas Adam, Nov 11, 2012
  2. 1/1 status: Allow for short-form via config optionThomas Adam, Nov 11, 2012
  3. Jeff KingNov 12, 2012

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.