summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-12-06 19:07:20 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-12-06 19:07:21 (GMT)
commitcb6bd5722f430b225b894920fd80975ffa1d0bb5 (patch)
treeb83e0610f305c21cd50ec4e5a5d2dc8625c02af3 /Documentation
parent10a36382ac2e53bbe8dec867c50ee11cc98724fc (diff)
parentdb64eb655b48ea2c635480c6cc992b0156817aeb (diff)
downloadgit-cb6bd5722f430b225b894920fd80975ffa1d0bb5.zip
git-cb6bd5722f430b225b894920fd80975ffa1d0bb5.tar.gz
git-cb6bd5722f430b225b894920fd80975ffa1d0bb5.tar.bz2
Merge branch 'rr/for-each-ref-decoration'
Add a few formatting directives to "git for-each-ref --format=...", to paint them in color, etc. * rr/for-each-ref-decoration: for-each-ref: avoid color leakage for-each-ref: introduce %(color:...) for color for-each-ref: introduce %(upstream:track[short]) for-each-ref: introduce %(HEAD) asterisk marker t6300 (for-each-ref): don't hardcode SHA-1 hexes t6300 (for-each-ref): clearly demarcate setup
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-for-each-ref.txt14
1 files changed, 13 insertions, 1 deletions
diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
index f2e08d1..94f5c46 100644
--- a/Documentation/git-for-each-ref.txt
+++ b/Documentation/git-for-each-ref.txt
@@ -91,7 +91,19 @@ objectname::
upstream::
The name of a local ref which can be considered ``upstream''
from the displayed ref. Respects `:short` in the same way as
- `refname` above.
+ `refname` above. Additionally respects `:track` to show
+ "[ahead N, behind M]" and `:trackshort` to show the terse
+ version: ">" (ahead), "<" (behind), "<>" (ahead and behind),
+ or "=" (in sync). Has no effect if the ref does not have
+ tracking information associated with it.
+
+HEAD::
+ '*' if HEAD matches current ref (the checked out branch), ' '
+ otherwise.
+
+color::
+ Change output color. Followed by `:<colorname>`, where names
+ are described in `color.branch.*`.
In addition to the above, for commit and tag objects, the header
field names (`tree`, `parent`, `object`, `type`, and `tag`) can