From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add date format --local-zone
Date: Wed, 25 Apr 2007 12:59:26 -0700 [thread overview]
Message-ID: <7vr6q8w7hd.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: alpine.LFD.0.98.0704250805440.9964@woody.linux-foundation.org
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Wed, 25 Apr 2007, Linus Torvalds wrote:
>>
>> Ie, it would be better, I think, to use a
>>
>> --date=local
>> --date=relative
>> --date=UTC
>> ...
>>
>> kind of syntax, than have each date flag be different ("--relative-date"
>> vs "--local-zone"?).
Probably.
> Btw, when you do "--local-zone", you should drop the TZ printout too, I
> think. It doesn't seem to make any sense to give the *wrong* timezone.
I do not think the definition of "wrong" is so clear.
I would not disagree that showing the authordate in timezone the
author was not in means --local-zone is showing a wrong zone,
but "show timestamps in _my_ zone" is what the option is
specifically asking for.
Originally I did it without timezone, but later I found it
amusing to see "log --since=2007-03-10 --until=2007-03-12".
Note: in TZ=US/Pacific you would see -0700 and -0800
during the above commit-time range.
next prev parent reply other threads:[~2007-04-25 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 6:36 [PATCH] Add date format --local-zone Junio C Hamano
2007-04-25 6:44 ` Shawn O. Pearce
2007-04-25 12:40 ` Johannes Schindelin
2007-04-25 15:03 ` Linus Torvalds
2007-04-25 15:22 ` Linus Torvalds
2007-04-25 19:59 ` Junio C Hamano [this message]
2007-04-25 20:12 ` Alex Riesen
2007-04-25 20:30 ` Junio C Hamano
2007-04-25 20:41 ` Alex Riesen
2007-04-25 21:02 ` Junio C Hamano
2007-04-26 4:56 ` [PATCH 1/2] Add --date={local,relative,default} Junio C Hamano
2007-04-26 6:54 ` David Kågedal
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=7vr6q8w7hd.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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).