diff options
author | Junio C Hamano <gitster@pobox.com> | 2020-09-09 15:27:44 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-09-09 15:27:44 -0700 |
commit | a65d8e6d1bb62324eb42aa11f71b3d3a02fc8523 (patch) | |
tree | 412f8218550a718e86ad46906047ac415c4af7e0 /git-for-each-ref.txt | |
parent | 558abd28b6851f370edc902b483e079a3ac255ab (diff) | |
download | git-htmldocs-a65d8e6d1bb62324eb42aa11f71b3d3a02fc8523.tar.gz |
Autogenerated HTML docs for v2.28.0-497-g54e85e
Diffstat (limited to 'git-for-each-ref.txt')
-rw-r--r-- | git-for-each-ref.txt | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/git-for-each-ref.txt b/git-for-each-ref.txt index 2ea71c5f6..616ce4608 100644 --- a/git-for-each-ref.txt +++ b/git-for-each-ref.txt @@ -222,6 +222,8 @@ worktreepath:: 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. +Fields `tree` and `parent` can also be used with modifier `:short` and +`:short=<length>` just like `objectname`. For commit and tag objects, the special `creatordate` and `creator` fields will correspond to the appropriate date or name-email-date tuple @@ -230,7 +232,10 @@ 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. +and `date` to extract the named component. For email fields (`authoremail`, +`committeremail` and `taggeremail`), `:trim` can be appended to get the email +without angle brackets, and `:localpart` to get the part before the `@` symbol +out of the trimmed email. The message in a commit or a tag object is `contents`, from which `contents:<part>` can be used to extract various parts out of: @@ -242,6 +247,9 @@ contents:subject:: The first paragraph of the message, which typically is a single line, is taken as the "subject" of the commit or the tag message. + Instead of `contents:subject`, field `subject` can also be used to + obtain same results. `:sanitize` can be appended to `subject` for + subject line suitable for filename. contents:body:: The remainder of the commit or the tag message that follows |