diff options
| author | Eric Wong <normalperson@yhbt.net> | 2016-01-05 03:51:57 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2016-01-05 17:44:19 (GMT) |
| commit | e914ef0d03d189611fe02e0fd26f5f964594767e (patch) | |
| tree | 65d38ff03ef0408987d392f85a56764e17cd7681 | |
| parent | 282616c72d1d08a77ca4fe1186cb708c38408d87 (diff) | |
| download | git-e914ef0d03d189611fe02e0fd26f5f964594767e.zip git-e914ef0d03d189611fe02e0fd26f5f964594767e.tar.gz git-e914ef0d03d189611fe02e0fd26f5f964594767e.tar.bz2 | |
for-each-ref: document `creatordate` and `creator` fields
These were introduced back in 2006 at 3175aa1ec28c but
never documented.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| -rw-r--r-- | Documentation/git-for-each-ref.txt | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt index 4240875..338a6ef 100644 --- a/Documentation/git-for-each-ref.txt +++ b/Documentation/git-for-each-ref.txt @@ -109,6 +109,11 @@ In addition to the above, for commit and tag objects, the header field names (`tree`, `parent`, `object`, `type`, and `tag`) can be used to specify the value in the header field. +For commit and tag objects, the special `creatordate` and `creator` +fields will correspond to the appropriate date or name-email-date tuple +from the `committer` or `tagger` fields depending on the object type. +These are intended for working on a mix of annotated and lightweight tags. + Fields that have name-email-date tuple as its value (`author`, `committer`, and `tagger`) can be suffixed with `name`, `email`, and `date` to extract the named component. @@ -119,8 +124,8 @@ 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`. -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. In any case, a field name that refers to a field inapplicable to |