Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
	 git@vger.kernel.org,  Josh McKinney <git-bugs@lists.joshka.net>
Subject: Re: [PATCH v2 0/3] refs/reftable: fix on-disk representation of reflog timezones
Date: Thu, 01 Oct 2026 10:11:01 -0700	[thread overview]
Message-ID: <xmqq33up73dm.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZRVt=e3MqjLY=UkitfSg_YjpsfFjeDsEmqJQm-5YhopxA@mail.gmail.com> (Karthik Nayak's message of "Thu, 1 Oct 2026 05:19:29 -0500")

Karthik Nayak <karthik.188@gmail.com> writes:

> Patrick Steinhardt <ps@pks.im> writes:
>
>> Hi,
>>
>> it was reported [1] that the way we store reflog timezones with the
>> reftable format has a mismatch with the reftable specification. While
>> the spec says that reftables should be stored as a signed offset in
>> minutes, we store them in the "[+-]HHMM" format that we typically use in
>> commit headers, for example.
>>
>> This patch series fixes this bug by making our on-disk representation
>> match the specification. This will of course make us reinterpret old
>> reftables. But ultimately, the fallout caused by this change is somewhat
>> limited as we only ever use reflog timezones for display purposes. So
>> yes, we'll display a wrong timezone. But it's not used as part of any
>> kind of computations.
>>
>> The series is built on top of v2.56.0.
>>
>> Changes in v2:
>>   - Improve readability of one of the converted sites that now use
>>     `minutes_to_tz()`.
>>   - Improve test coverage.
>>   - Link to v1: https://patch.msgid.link/20260929-pks-reftables-fix-timezone-format-v1-0-3df105a95ed1@pks.im
>>
>
> The range-diff looks in order. This version looks good to me!

Thanks for writing and reviewing.  The previous round was good
enough already but with an extra polish, this looks really ready.

Will mark the topic for 'next'.

      reply	other threads:[~2026-10-01 17:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29  9:56 [PATCH 0/3] refs/reftable: fix on-disk representation of reflog timezones Patrick Steinhardt
2026-09-29  9:56 ` [PATCH 1/3] date: add helpers to convert between "+HHMM" timezones and minutes Patrick Steinhardt
2026-09-30 11:47   ` Karthik Nayak
2026-09-30 12:05     ` Patrick Steinhardt
2026-10-01 10:18       ` Karthik Nayak
2026-09-30 19:54     ` Junio C Hamano
2026-09-29  9:56 ` [PATCH 2/3] t/helper: fix segfault in "dump-reftable -t" Patrick Steinhardt
2026-09-29  9:56 ` [PATCH 3/3] refs/reftable: fix on-disk representation of reflog timezones Patrick Steinhardt
2026-09-30 11:51   ` Karthik Nayak
2026-09-30 12:05     ` Patrick Steinhardt
2026-10-01  5:38 ` [PATCH v2 0/3] " Patrick Steinhardt
2026-10-01  5:39   ` [PATCH v2 1/3] date: add helpers to convert between "+HHMM" timezones and minutes Patrick Steinhardt
2026-10-01  5:39   ` [PATCH v2 2/3] t/helper: fix segfault in "dump-reftable -t" Patrick Steinhardt
2026-10-01  5:39   ` [PATCH v2 3/3] refs/reftable: fix on-disk representation of reflog timezones Patrick Steinhardt
2026-10-01 10:19   ` [PATCH v2 0/3] " Karthik Nayak
2026-10-01 17:11     ` 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=xmqq33up73dm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git-bugs@lists.joshka.net \
    --cc=git@vger.kernel.org \
    --cc=karthik.188@gmail.com \
    --cc=ps@pks.im \
    /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