All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chengwei Ding <waterding@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Eugene Letuchy <eugene@facebook.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git annotate with date option not working?
Date: Wed, 1 Jun 2011 18:28:43 +0200	[thread overview]
Message-ID: <1805632198775747949@unknownmsgid> (raw)
In-Reply-To: <20110601161638.GB7132@sigill.intra.peff.net>

Thx Peff, this really helps. So then doc on this cmd is outdated. Have
been used to emacs build-in vc which call annotate (rumor say it will
support git blame), anyway, have switch to other emacs git plugin now.

Thanks

发自我的 iPhone

在 Jun 1, 2011,18:16,Jeff King <peff@peff.net> 写道:

> On Wed, Jun 01, 2011 at 10:20:37AM +0200, Chengwei Ding wrote:
>
>> can anyone confirm that this "--date" option is working for git
>> annotate cmd.
>
> This is by design:
>
>  $ git show 31653c1abc1ac80206db9efca56ff1969150d8fe
>  Author: Eugene Letuchy <eugene@facebook.com>
>  Date:   Fri Feb 20 14:51:11 2009 -0800
>  [...]
>      git annotate ignores the date format specifiers and continues to
>      uses the ISO format, as before.
>  [...]
>  +       if (cmd_is_annotate) {
>                  output_option |= OUTPUT_ANNOTATE_COMPAT;
>  +               blame_date_mode = DATE_ISO8601;
>  +       } else {
>  +               blame_date_mode = revs.date_mode;
>  +       }
>
> The annotate command is a historical artifact, and will remain frozen in
> time in terms of output format and features. If you want to use newer
> features, use "git blame". If you really need the annotate output format
> with newer blame features, use "git blame -c".
>
> -Peff

  reply	other threads:[~2011-06-01 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01  8:20 git annotate with date option not working? Chengwei Ding
2011-06-01  9:40 ` Jakub Narebski
2011-06-01 12:31   ` Chengwei Ding
2011-06-01  9:41 ` Arnaud Lacurie
2011-06-01 12:33   ` Chengwei Ding
2011-06-01 16:16 ` Jeff King
2011-06-01 16:28   ` Chengwei Ding [this message]
2011-06-01 16:49   ` Jeff King
2011-06-01 19:37     ` Jonathan Nieder

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=1805632198775747949@unknownmsgid \
    --to=waterding@gmail.com \
    --cc=eugene@facebook.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.