# [PATCH] git-for-each-ref.txt: 'raw' is a supported date format 3 messages from 2013-01-21 to 2013-01-21. Participants: John Keeping, Michael Haggerty. Thread: https://gitlist.dev/t/32684 ## John Keeping, 2013-01-21 13:53 Subject: [PATCH] git-for-each-ref.txt: 'raw' is a supported date format Message-ID: URL: https://gitlist.dev/e/d3a288a67867d7a60c9217a78bda42301392c3da.1358776352.git.john%40keeping.me.uk ``` Commit 7dff9b3 (Support 'raw' date format) added a raw date format. Update the git-for-each-ref documentation to include this. Signed-off-by: John Keeping --- Documentation/git-for-each-ref.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt index db55a4e..d3e1df7 100644 --- a/Documentation/git-for-each-ref.txt +++ b/Documentation/git-for-each-ref.txt @@ -117,7 +117,7 @@ returns an empty string instead. As a special case for the date-type fields, you may specify a format for the date by adding one of `:default`, `:relative`, `:short`, `:local`, -`:iso8601` or `:rfc2822` to the end of the fieldname; e.g. +`:iso8601`, `:rfc2822` or `raw` to the end of the fieldname; e.g. `%(taggerdate:relative)`. -- 1.8.1 ``` ## Michael Haggerty, 2013-01-21 16:02 Subject: Re: [PATCH] git-for-each-ref.txt: 'raw' is a supported date format Message-ID: <50FD66AC.1080201@alum.mit.edu> URL: https://gitlist.dev/e/50FD66AC.1080201%40alum.mit.edu In-Reply-To: ``` On 01/21/2013 02:53 PM, John Keeping wrote: > Commit 7dff9b3 (Support 'raw' date format) added a raw date format. > Update the git-for-each-ref documentation to include this. > > Signed-off-by: John Keeping > --- > Documentation/git-for-each-ref.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt > index db55a4e..d3e1df7 100644 > --- a/Documentation/git-for-each-ref.txt > +++ b/Documentation/git-for-each-ref.txt > @@ -117,7 +117,7 @@ returns an empty string instead. > > As a special case for the date-type fields, you may specify a format for > the date by adding one of `:default`, `:relative`, `:short`, `:local`, > -`:iso8601` or `:rfc2822` to the end of the fieldname; e.g. > +`:iso8601`, `:rfc2822` or `raw` to the end of the fieldname; e.g. > `%(taggerdate:relative)`. Shouldn't "raw" be preceded with a colon like the other format specifiers? Michael -- Michael Haggerty mhagger@alum.mit.edu http://softwareswirl.blogspot.com/ ``` ## John Keeping, 2013-01-21 16:22 Subject: [PATCH v2] git-for-each-ref.txt: 'raw' is a supported date format Message-ID: <20130121162206.GG7498@serenity.lan> URL: https://gitlist.dev/e/20130121162206.GG7498%40serenity.lan In-Reply-To: <50FD66AC.1080201@alum.mit.edu> ``` Commit 7dff9b3 (Support 'raw' date format) added a raw date format. Update the git-for-each-ref documentation to include this. Signed-off-by: John Keeping --- On Mon, Jan 21, 2013 at 05:02:52PM +0100, Michael Haggerty wrote: > Shouldn't "raw" be preceded with a colon like the other format specifiers? Yes it should. Thanks. Documentation/git-for-each-ref.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt index db55a4e..d3e1df7 100644 --- a/Documentation/git-for-each-ref.txt +++ b/Documentation/git-for-each-ref.txt @@ -117,7 +117,7 @@ returns an empty string instead. As a special case for the date-type fields, you may specify a format for the date by adding one of `:default`, `:relative`, `:short`, `:local`, -`:iso8601` or `:rfc2822` to the end of the fieldname; e.g. +`:iso8601`, `:rfc2822` or `:raw` to the end of the fieldname; e.g. `%(taggerdate:relative)`. -- 1.8.1.353.gc992d5a.dirty ```