From: Junio C Hamano <gitster@pobox.com>
To: eugene@facebook.com
Cc: "eletuchy@gmail.com" <eletuchy@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] adds --date=raw support to git blame and related documentation
Date: Mon, 23 Feb 2009 17:35:20 -0800 [thread overview]
Message-ID: <7v3ae4pqg7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 49A2E170.9030807@facebook.com
Eugene Letuchy <eletuchy@facebook.com> writes:
> On 2/23/09 9:10 AM, Junio C Hamano wrote:
>> eletuchy@gmail.com writes:
>>
>>> From: Eugene Letuchy<eugene@facebook.com>
>>>
>>> In the wake of Linus' 7dff9b3, git blame --date support needs to
>>> incorporate --date=raw in addition to the previously supported
>>> date formats.
>>
>> Thanks, but I do not understand what you meant by the following two lines:
>>
>>> Test:> git grep relative | grep iso | grep -v raw
>>> > git blame --date=raw builtin-blame.c
>>
>> With the patch to add --date=raw format already on 'master', I'd prefer a
>> reroll of the original patch (it needs a fix for the config "don't ignore
>> a misconfiguration" bug Peff pointed out anyway) with this documentation
>> update patch squashed in.
>>
>
> Yeah I can do that.
Thanks.
>>> diff --git a/Documentation/blame-options.txt b/Documentation/blame-options.txt
>>> index e6717af..1316d4e 100644
>>> --- a/Documentation/blame-options.txt
>>> +++ b/Documentation/blame-options.txt
>>> @@ -36,7 +36,7 @@ of lines before or after the line given by<start>.
>>> Show long rev (Default: off).
>>>
>>> -t::
>>> - Show raw timestamp (Default: off).
>>> + Synomym for --date=raw (Default: off).
>>
>> This is interesting. It suggests that we should internally get rid of
>> show_raw_time variable (and need to error out when --date= and -t options
>> are given at the same time, as they are mutually incompatible).
>>
>> But do -t and --date=raw really behave identically? I think they should
>> but I didn't check.
>>
>
> The output of -t and --date=raw are exactly identical (well, after
> this patch they are); for that reason, I think providing both is
> redundant but not an error. However, I wanted to retain -t for "git
> annotate" compatibility, which has -t as the sole date option. In
> git-annotate mode, no other --date mode options can apply.
Oh, I didn't mean combination of -t and --date=raw. Consider a
combination such as -t and --date=iso given together.
The removal of show_raw_time would be a good idea if -t and --date=raw
are meant to be identical, right?
prev parent reply other threads:[~2009-02-24 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 8:57 [PATCH] adds --date=raw support to git blame and related documentation eletuchy
2009-02-23 17:10 ` Junio C Hamano
2009-02-23 17:48 ` Eugene Letuchy
2009-02-24 1:35 ` 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=7v3ae4pqg7.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=eletuchy@gmail.com \
--cc=eugene@facebook.com \
--cc=git@vger.kernel.org \
/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).