| commit | 547ed71636dbfab2dc303ba8cabb29c2cab22f1e | |
| author | Jeff King <peff@peff.net> | |
| Thu, 3 Sep 2015 21:48:55 +0000 (3 22:48 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 3 Sep 2015 22:36:34 +0000 (3 15:36 -0700) | ||
| tree | abbc66c2239f07b8ee643b30ea39c48d76414bc0 | treesnapshot (tar.gz zip) |
| parent | 4b1c5e1d268fa1e7b4344e7d94de1edc5ead49a5 | commitdiff |
fast-import: switch crash-report date to iso8601
When fast-import emits a crash report, it does so in the
user's local timezone. But because we omit the timezone
completely for DATE_LOCAL, a reader of the report does not
immediately know which time zone was used. Let's switch this
to ISO8601 instead, which includes the time zone.
This does mean we will show the time in UTC, but that's not
a big deal. A crash report like this will either be looked
at immediately (in which case nobody even looks at the
timestamp), or it will be passed along to a developer to
debug, in which case the original timezone is less likely to
be of interest.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: John Keeping <john@keeping.me.uk>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When fast-import emits a crash report, it does so in the
user's local timezone. But because we omit the timezone
completely for DATE_LOCAL, a reader of the report does not
immediately know which time zone was used. Let's switch this
to ISO8601 instead, which includes the time zone.
This does mean we will show the time in UTC, but that's not
a big deal. A crash report like this will either be looked
at immediately (in which case nobody even looks at the
timestamp), or it will be passed along to a developer to
debug, in which case the original timezone is less likely to
be of interest.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: John Keeping <john@keeping.me.uk>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| fast-import.c | diffblobblamehistory |