From: Thomas Adam <thomas@xteddy.org>
To: git@vger.kernel.org
Cc: Thomas Adam <thomas@xteddy.org>
Subject: [RFC PATCH 0/1] status: Allow for short-form output by default
Date: Sun, 11 Nov 2012 22:53:02 +0000 [thread overview]
Message-ID: <1352674383-23654-1-git-send-email-thomas@xteddy.org> (raw)
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 reply other threads:[~2012-11-11 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 22:53 Thomas Adam [this message]
2012-11-11 22:53 ` [RFC PATCH 1/1] status: Allow for short-form via config option Thomas Adam
2012-11-12 21:17 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1352674383-23654-1-git-send-email-thomas@xteddy.org \
--to=thomas@xteddy.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).