From: Theodore Ts'o <tytso@mit.edu>
To: Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 4/5] date: document and test "raw-local" mode
Date: Mon, 11 Jul 2016 12:50:00 -0400 [thread overview]
Message-ID: <20160711165000.GD3890@thunk.org> (raw)
In-Reply-To: <20160711050617.GD32514@sigill.intra.peff.net>
On Mon, Jul 11, 2016 at 01:06:17AM -0400, Jeff King wrote:
>
> The documentation claims that "raw-local" does not work. It
> does, but the end result is rather subtle. Let's describe it
> in better detail, and test to make sure it works (namely,
> the epoch time doesn't change, but the zone does).
Maybe add an editorial statement that in most cases this isn't
particularly useful? Documenting raw-local implies that someone might
want to consider using it, and it's not clear to me folks should ever
try --- they're more likely to confuse themselves more than anything
else.
- Ted
next prev parent reply other threads:[~2016-07-11 16:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 5:54 [PATCH] pretty: add format specifiers: %gr, %gt, %gI, gi Theodore Ts'o
2016-07-10 6:16 ` Jeff King
2016-07-10 14:26 ` Theodore Ts'o
2016-07-10 16:05 ` Duy Nguyen
2016-07-10 23:28 ` Theodore Ts'o
2016-07-11 5:02 ` Jeff King
2016-07-11 5:03 ` [PATCH 1/5] doc/rev-list-options: clarify "commit@{Nth}" for "-g" option Jeff King
2016-07-11 5:04 ` [PATCH 2/5] doc/rev-list-options: explain "-g" output formats Jeff King
2016-07-11 5:05 ` [PATCH 3/5] doc/pretty-formats: describe index/time formats for %gd Jeff King
2016-07-11 16:48 ` Theodore Ts'o
2016-07-12 0:08 ` Jeff King
2016-07-12 2:01 ` Junio C Hamano
2016-07-11 5:06 ` [PATCH 4/5] date: document and test "raw-local" mode Jeff King
2016-07-11 16:50 ` Theodore Ts'o [this message]
2016-07-12 0:16 ` Jeff King
2016-07-11 5:07 ` [PATCH 5/5] date: add "unix" format Jeff King
2016-07-11 16:43 ` [PATCH] pretty: add format specifiers: %gr, %gt, %gI, gi Theodore Ts'o
2016-07-11 19:07 ` 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=20160711165000.GD3890@thunk.org \
--to=tytso@mit.edu \
--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.