From: Michael Haggerty <mhagger@alum.mit.edu>
To: John Keeping <john@keeping.me.uk>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-for-each-ref.txt: 'raw' is a supported date format
Date: Mon, 21 Jan 2013 17:02:52 +0100 [thread overview]
Message-ID: <50FD66AC.1080201@alum.mit.edu> (raw)
In-Reply-To: <d3a288a67867d7a60c9217a78bda42301392c3da.1358776352.git.john@keeping.me.uk>
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 <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/
next prev parent reply other threads:[~2013-01-21 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 13:53 [PATCH] git-for-each-ref.txt: 'raw' is a supported date format John Keeping
2013-01-21 16:02 ` Michael Haggerty [this message]
2013-01-21 16:22 ` [PATCH v2] " John Keeping
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50FD66AC.1080201@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.