From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: "Mladen B." <mladen074@gmail.com>
Subject: [PATCH] config,completion: add color.status.unmerged
Date: Tue, 10 Mar 2015 17:11:09 +0100 [thread overview]
Message-ID: <1e27ed382c4dc09ee5993b828c16b89e34d1cdf4.1426003811.git.git@drmicha.warpmail.net> (raw)
In-Reply-To: <CAKHLQpFPJS2rp-QswBSmO72yx253LZC-LTZCimk+f+un0tAWZg@mail.gmail.com>
Reported-by: "Mladen B." <mladen074@gmail.com>
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
Documentation/config.txt | 6 ++++--
contrib/completion/git-completion.bash | 1 +
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index a158e7f..bc22eee 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -958,9 +958,11 @@ color.status.<slot>::
`added` or `updated` (files which are added but not committed),
`changed` (files which are changed but not added in the index),
`untracked` (files which are not tracked by Git),
- `branch` (the current branch), or
+ `branch` (the current branch),
`nobranch` (the color the 'no branch' warning is shown in, defaulting
- to red). The values of these variables may be specified as in
+ to red), or
+ `unmerged` (files which have unmerged changes).
+ The values of these variables may be specified as in
color.branch.<slot>.
color.ui::
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index c21190d..e310f31 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -2014,6 +2014,7 @@ _git_config ()
color.status.changed
color.status.header
color.status.nobranch
+ color.status.unmerged
color.status.untracked
color.status.updated
color.ui
--
2.3.2.346.gb6960c9
prev parent reply other threads:[~2015-03-10 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 12:44 Missing slot "unmerged" Mladen B.
2015-03-10 16:11 ` Michael J Gruber [this message]
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=1e27ed382c4dc09ee5993b828c16b89e34d1cdf4.1426003811.git.git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=mladen074@gmail.com \
/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).