{"thread":{"id":"41123","subject":"[PATCH] for-each-ref: document `creatordate` and `creator` fields","startedAt":"2016-01-05T03:51:57Z","lastAt":"2016-01-05T17:43:12Z","messageCount":2,"participants":["Eric Wong","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"275344","messageId":"20160105035157.GA1212@dcvr.yhbt.net","threadId":"41123","inReplyTo":null,"subject":"[PATCH] for-each-ref: document `creatordate` and `creator` fields","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2016-01-05T03:51:57Z","receivedAt":"2016-01-05T03:51:57Z","isPatch":true,"sender":{"key":"e@80x24.org","avatar":null},"body":"These were introduced back in 2006 at 3175aa1ec28c but\nnever documented.\n\nSigned-off-by: Eric Wong <normalperson@yhbt.net>\n---\n And I just found these very useful, today!\n\n I also noticed creator{name,email} aren't supported, yet.\n Perhaps they're worth implementing for consistency.\n\n Documentation/git-for-each-ref.txt | 9 +++++++--\n 1 file changed, 7 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex c6f073c..06208c4 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -142,6 +142,11 @@ In addition to the above, for commit and tag objects, the header\n field names (`tree`, `parent`, `object`, `type`, and `tag`) can\n be used to specify the value in the header field.\n \n+For commit and tag objects, the special `creatordate` and `creator`\n+fields will correspond to the appropriate date or name-email-date tuple\n+from the `committer` or `tagger` fields depending on the object type.\n+These are intended for working on a mix of annotated and lightweight tags.\n+\n Fields that have name-email-date tuple as its value (`author`,\n `committer`, and `tagger`) can be suffixed with `name`, `email`,\n and `date` to extract the named component.\n@@ -153,8 +158,8 @@ line is 'contents:body', where body is all of the lines after the first\n blank line.  The optional GPG signature is `contents:signature`.  The\n first `N` lines of the message is obtained using `contents:lines=N`.\n \n-For sorting purposes, fields with numeric values sort in numeric\n-order (`objectsize`, `authordate`, `committerdate`, `taggerdate`).\n+For sorting purposes, fields with numeric values sort in numeric order\n+(`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`).\n All other fields are used to sort in their byte-value order.\n \n There is also an option to sort by versions, this can be done by using\n-- \nEW\n"},{"id":"275388","messageId":"xmqqoaczkjm7.fsf@gitster.mtv.corp.google.com","threadId":"41123","inReplyTo":"20160105035157.GA1212@dcvr.yhbt.net","subject":"Re: [PATCH] for-each-ref: document `creatordate` and `creator` fields","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-01-05T17:43:12Z","receivedAt":"2016-01-05T17:43:12Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Eric Wong <normalperson@yhbt.net> writes:\n\n> These were introduced back in 2006 at 3175aa1ec28c but\n> never documented.\n\nThanks, and I totally forgot about the feature ;-)\n\n> Signed-off-by: Eric Wong <normalperson@yhbt.net>\n> ---\n>  And I just found these very useful, today!\n>\n>  I also noticed creator{name,email} aren't supported, yet.\n>  Perhaps they're worth implementing for consistency.\n>\n>  Documentation/git-for-each-ref.txt | 9 +++++++--\n>  1 file changed, 7 insertions(+), 2 deletions(-)\n>\n> diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\n> index c6f073c..06208c4 100644\n> --- a/Documentation/git-for-each-ref.txt\n> +++ b/Documentation/git-for-each-ref.txt\n> @@ -142,6 +142,11 @@ In addition to the above, for commit and tag objects, the header\n>  field names (`tree`, `parent`, `object`, `type`, and `tag`) can\n>  be used to specify the value in the header field.\n>  \n> +For commit and tag objects, the special `creatordate` and `creator`\n> +fields will correspond to the appropriate date or name-email-date tuple\n> +from the `committer` or `tagger` fields depending on the object type.\n> +These are intended for working on a mix of annotated and lightweight tags.\n> +\n>  Fields that have name-email-date tuple as its value (`author`,\n>  `committer`, and `tagger`) can be suffixed with `name`, `email`,\n>  and `date` to extract the named component.\n> @@ -153,8 +158,8 @@ line is 'contents:body', where body is all of the lines after the first\n>  blank line.  The optional GPG signature is `contents:signature`.  The\n>  first `N` lines of the message is obtained using `contents:lines=N`.\n>  \n> -For sorting purposes, fields with numeric values sort in numeric\n> -order (`objectsize`, `authordate`, `committerdate`, `taggerdate`).\n> +For sorting purposes, fields with numeric values sort in numeric order\n> +(`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`).\n>  All other fields are used to sort in their byte-value order.\n>  \n>  There is also an option to sort by versions, this can be done by using\n"}]}