git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Letuchy <eletuchy@facebook.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	"marius@trolltech.com" <marius@trolltech.com>,
	<gitster@pobox.com>
Subject: Re: [PATCH] Make git blame date output format configurable, a la git log
Date: Fri, 20 Feb 2009 05:55:19 -0800	[thread overview]
Message-ID: <499EB647.30606@facebook.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0902201434460.6302@intel-tinevez-2-302>

Hi Johannes,

Thanks for your feedback. Any comments on the .c changes?

I'll modify the commit message to read as follows:
"""

Add the following:
  - git config value blame.date that expects one of the git log date
    formats ({relative,local,default,iso,rfc,short})
  - git blame command line option --date-format expects one of the git
    log date formats ({relative,local,default,iso,rfc,short})
  - documentation in blame-options.txt
  - git blame uses the appropriate date.c functions and enums to
    make sense of the date format and provide appropriate data

The tests pass. The mailmap test needed to be modified to expect iso
formatted blames rather than the new "default".

Signed-off-by: Eugene Letuchy <eugene@facebook.com>
"""

-Eugene

+ cc: junio

On 2/20/09 5:40 AM, Johannes Schindelin wrote:
> Hi,
>
> Disclaimer: if you are offended by constructive criticism, or likely to
> answer with insults to the comments I offer, please stop reading this mail
> now (and please to not answer my mail, either). :-)
>
> Still with me?  Good.  Nice to meet you.
>
> Just out of curiosity: why Cc: Marius?  I would have expected Junio, Git's
> maintainer.
>
> May I suggest the commit subject to say "as for git log"?  I mistook "a la
> git log" for a change in the way git-blame works...
>
> On Fri, 20 Feb 2009, eletuchy@gmail.com wrote:
>
>> From: Eugene Letuchy<eugene@facebook.com>
>>
>> Adds the following:
>
> We try to use the imperative form; from my experience it makes for an
> easier read: "Add the following:"
>
>>   - git config value blame.date that expects one of the git log date
>>     formats ({relative,local,default,iso,rfc,short})
>>   - git blame command line option --date-format expects one of the git
>>     log date formats ({relative,local,default,iso,rfc,short})
>>   - documentation in blame-options.txt
>>   - git blame uses the appropriate date.c functions and enums to
>>     make sense of the date format and provide appropriate data
>>
>> The tests pass. The mailmap test needed to be modified to expect iso
>> formatted blames rather than the new "default".
>
> IMHO the "The tests pass." should be removed.
>
> Other than that, nicely done!
>
> Ciao,
> Dscho
>

  reply	other threads:[~2009-02-20 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 13:24 [PATCH] Make git blame date output format configurable, a la git log eletuchy
2009-02-20 13:40 ` Johannes Schindelin
2009-02-20 13:55   ` Eugene Letuchy [this message]
2009-02-20 13:57     ` Eugene Letuchy
2009-02-20 14:06     ` Johannes Schindelin
2009-02-20 14:27 ` Jeff King
2009-02-20 16:13   ` Eugene Letuchy
2009-02-20 17:18     ` Jeff King
2009-02-20 16:59 ` Junio C Hamano

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=499EB647.30606@facebook.com \
    --to=eletuchy@facebook.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=eletuchy@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=marius@trolltech.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).