From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 20 Jan 2016 19:43:30 +0000 (-0800)
Subject: Merge branch 'ew/for-each-ref-doc'
X-Git-Tag: v2.8.0-rc0~113
X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/108cb77c868b541bb9bee43e9bfe9310827e1eb7

Merge branch 'ew/for-each-ref-doc'

* ew/for-each-ref-doc:
for-each-ref: document `creatordate` and `creator` fields
---

108cb77c868b541bb9bee43e9bfe9310827e1eb7
diff --cc Documentation/git-for-each-ref.txt
index c6f073cea4,338a6efa81..06208c4990
--- a/Documentation/git-for-each-ref.txt
+++ b/Documentation/git-for-each-ref.txt
@@@ -150,16 -122,12 +155,16 @@@ The complete message in a commit and ta
  Its first line is `contents:subject`, where subject is the concatenation
  of all lines of the commit message up to the first blank line.  The next
  line is 'contents:body', where body is all of the lines after the first
 -blank line.  Finally, the optional GPG signature is `contents:signature`.
 +blank line.  The optional GPG signature is `contents:signature`.  The
 +first `N` lines of the message is obtained using `contents:lines=N`.
  
- For sorting purposes, fields with numeric values sort in numeric
- order (`objectsize`, `authordate`, `committerdate`, `taggerdate`).
+ For sorting purposes, fields with numeric values sort in numeric order
+ (`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`).
  All other fields are used to sort in their byte-value order.
  
 +There is also an option to sort by versions, this can be done by using
 +the fieldname `version:refname` or its alias `v:refname`.
 +
  In any case, a field name that refers to a field inapplicable to
  the object referred by the ref does not cause an error.  It
  returns an empty string instead.