From: Junio C Hamano <gitster@pobox.com>
To: Thomas Braun <thomas.braun@virtuell-zuhause.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/1] pretty: note that %cd respects the --date= option
Date: Thu, 21 Aug 2014 13:07:12 -0700 [thread overview]
Message-ID: <xmqqr409r4i7.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53F4941E.2060201@virtuell-zuhause.de> (Thomas Braun's message of "Wed, 20 Aug 2014 14:27:10 +0200")
Thomas Braun <thomas.braun@virtuell-zuhause.de> writes:
> Signed-off-by: Thomas Braun <thomas.braun@virtuell-zuhause.de>
> ---
>
> Today I found out that both %cd and %ad pretty print format
> specifications honour the --date option as shown in:
>
> $ git log --abbrev=8 --date=short --pretty="%h (%s, %cd)" -n1
> 5bdb1c4e (Merge pull request #245 from
> kblees/kb/master/fix-libsvn-address-conflict, 2014-08-16)
> $ git log --abbrev=8 --date=short --pretty="%h (%s, %ad)" -n1
> 5bdb1c4e (Merge pull request #245 from
> kblees/kb/master/fix-libsvn-address-conflict, 2014-08-16)
>
> But the documentation did not mention that.
>
> Documentation/pretty-formats.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/pretty-formats.txt
> b/Documentation/pretty-formats.txt
> index 85d6353..eac7909 100644
> --- a/Documentation/pretty-formats.txt
> +++ b/Documentation/pretty-formats.txt
> @@ -122,7 +122,7 @@ The placeholders are:
> - '%ce': committer email
> - '%cE': committer email (respecting .mailmap, see
> linkgit:git-shortlog[1] or linkgit:git-blame[1])
> -- '%cd': committer date
> +- '%cd': committer date (format respects --date= option)
Funny that we already have the same text for %ad. Thanks.
> - '%cD': committer date, RFC2822 style
> - '%cr': committer date, relative
> - '%ct': committer date, UNIX timestamp
prev parent reply other threads:[~2014-08-21 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 12:27 [PATCH 1/1] pretty: note that %cd respects the --date= option Thomas Braun
2014-08-21 20:07 ` Junio C Hamano [this message]
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=xmqqr409r4i7.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=thomas.braun@virtuell-zuhause.de \
/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.