development/git
development/git
1
0
Fork 0
mirror of https://github.com/git/git synced 2024-08-25 02:35:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse source 
* ew/for-each-ref-doc:
  for-each-ref: document `creatordate` and `creator` fields
This commit is contained in:
Junio C Hamano 2016-02-05 14:54:19 -08:00
parent 353f685572 e914ef0d03
commit 01517bd26f
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
Documentation/git-for-each-ref.txt
View file

@ -146,6 +146,11 @@ In addition to the above, for commit and tag objects, the header
field names (`tree`, `parent`, `object`, `type`, and `tag`) can field names (`tree`, `parent`, `object`, `type`, and `tag`) can
be used to specify the value in the header field. 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`, Fields that have name-email-date tuple as its value (`author`,
`committer`, and `tagger`) can be suffixed with `name`, `email`, `committer`, and `tagger`) can be suffixed with `name`, `email`,
and `date` to extract the named component. and `date` to extract the named component.
@ -157,8 +162,8 @@ line is 'contents:body', where body is all of the lines after the first
blank line. The optional GPG signature is `contents:signature`. The blank line. The optional GPG signature is `contents:signature`. The
first `N` lines of the message is obtained using `contents:lines=N`. first `N` lines of the message is obtained using `contents:lines=N`.
For sorting purposes, fields with numeric values sort in numeric For sorting purposes, fields with numeric values sort in numeric order
order (`objectsize`, `authordate`, `committerdate`, `taggerdate`). (`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`).
All other fields are used to sort in their byte-value order. 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 There is also an option to sort by versions, this can be done by using