Subject: Re: [PATCH] git-for-each-ref.txt: 'raw' is a supported date format

From: Michael Haggerty <[email-masked]>
Date: Mon, 21 Jan 2013 17:02:52 +0100

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 <[email-masked]>
> ---
>  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
[email-masked]
http://softwareswirl.blogspot.com/