git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Timezone with DATE_STRFTIME

From
Jeff King <peff@peff.net>
Date
Feb 8, 2016, 15:28 UTC
Message-ID
<20160208152858.GA17226@sigill.intra.peff.net>
In-Reply-To
<20160208143317.GN29880@serenity.lan>
On Mon, Feb 08, 2016 at 02:33:17PM +0000, John Keeping wrote:
Show 6 quoted lines
> I have just noticed that with DATE_STRFTIME, the timezone in the output
> is likely to be incorrect.
> 
> For all other time formats, we print the string ourselves and use the
> correct timezone from the input, but with DATE_STRFTIME strftime(3) will
> always use the system timezone.

You mean here that the "%z" formatting will not be correct, right? AFAICT the time shown is generally correct for the original of the author, and we simply need to communicate the zone to strftime.

Taking the current tip of master, for instance, I get:
  $ for i in \
      default \
      local \
      "format:%H:%M %z" \
      "format-local:%H:%M %z"; do
            git log -1 --format=%ad --date="$i" ff4ea6004
    done
  Fri Feb 5 15:24:02 2016 -0800
  Fri Feb 5 18:24:02 2016
  15:24 +0000
  18:24 +0000

You can see that my system is in -0500, three hours ahead of the author. And as expected, strftime shows the time in the original author's timezone. The %z information is totally bogus, but I don't think it has anything to do with the system time. It is simply that we don't provide it (...but having just looked at _your_ local timezone from your email, I can guess how you got confused :) ).

So I think the fix is probably just that we need to feed the zone information to strftime via the "struct tm".

-Peff
Previous: John KeepingNext: Jeff King
Message 2 of 4 in “Timezone with DATE_STRFTIME”
  1. John KeepingFeb 8, 2016
  2. Jeff KingFeb 8, 2016
  3. Jeff KingFeb 8, 2016
  4. John KeepingFeb 8, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.