threads / patch / 32684

patchgit-for-each-ref.txt: 'raw' is a supported date format

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

## tl;dr

3 messages between Jan 21, 2013 and Jan 21, 2013. Diffs are folded; open one to read it.

replies: 2people: 2as markdown or json

John Keeping· Jan 21, 2013, 13:53 UTC · lore

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 <john@keeping.me.uk>
---
 Documentation/git-for-each-ref.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Show changes to Documentation/git-for-each-ref.txt +1 −1

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· Jan 21, 2013, 16:02 UTC · re: John Keeping · lore

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

On 01/21/2013 02:53 PM, John Keeping wrote:

Show 19 quoted lines

> 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 <john@keeping.me.uk>
> ---
>  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· Jan 21, 2013, 16:22 UTC · re: Michael Haggerty · lore

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

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 <john@keeping.me.uk>
---
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(-)

Show changes to Documentation/git-for-each-ref.txt +1 −1

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