From: Junio C Hamano <gitster@pobox.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: git <git@vger.kernel.org>,
Abhishek Kumar <abhishekkumar8222@gmail.com>,
Derrick Stolee <stolee@gmail.com>, Taylor Blau <me@ttaylorr.com>
Subject: Re: What's cooking in git.git (Sep 2020, #03; Wed, 9)
Date: Tue, 15 Sep 2020 14:45:51 -0700
Message-ID: <xmqqzh5qyar4.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CANQwDwc3-n4X16F1Xuf-y-yLeXoGRTeT5c=kVVFXH1E6P=ZEqA@mail.gmail.com> ("Jakub =?utf-8?Q?Nar=C4=99bski=22's?= message of "Tue, 15 Sep 2020 23:25:16 +0200")
Jakub Narębski <jnareb@gmail.com> writes:
>> My gut feeling is that overflow handling needs to be there whether the
>> field is 32-bit or 64-bit.
>
> Not if the size on-disk is the same as the size in memory:
> timestamp_t is usually 64 bit (and even unsigned 64 bit epoch
> would be enough - its range is over twenty times the present
> age of the universe per direction).
Yes, and "corrected commit dates" is about accommodating commits
with absurd out-of-sync timestamp mixed in a history with commits
with correct timestamp, right? What happens if the absurd timestamp
is near the limit of the range? You do not have to live through the
end of the universe---you only have to create a commit object that
records such a timestamp, no?
next prev parent reply other threads:[~2020-09-15 21:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 22:32 Junio C Hamano
2020-09-09 23:07 ` Eric Sunshine
2020-09-10 4:52 ` Junio C Hamano
2020-09-15 22:48 ` Eric Sunshine
2020-09-15 22:54 ` Junio C Hamano
2020-09-15 19:05 ` Jakub Narębski
2020-09-15 19:32 ` Taylor Blau
2020-09-15 21:14 ` Junio C Hamano
2020-09-15 21:25 ` Jakub Narębski
2020-09-15 21:45 ` Junio C Hamano [this message]
2020-09-15 21:48 ` Taylor Blau
2020-09-15 22:32 ` Junio C Hamano
2020-09-15 22:02 ` Jakub Narębski
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzh5qyar4.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=abhishekkumar8222@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=me@ttaylorr.com \
--cc=stolee@gmail.com \
/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
git@vger.kernel.org list mirror (unofficial, one of many)
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://public-inbox.org/git
git clone --mirror http://ou63pmih66umazou.onion/git
git clone --mirror http://czquwvybam4bgbro.onion/git
git clone --mirror http://hjrcffqmbrq6wope.onion/git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V1 git git/ https://public-inbox.org/git \
git@vger.kernel.org
public-inbox-index git
Example config snippet for mirrors.
Newsgroups are available over NNTP:
nntp://news.public-inbox.org/inbox.comp.version-control.git
nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
nntp://news.gmane.io/gmane.comp.version-control.git
note: .onion URLs require Tor: https://www.torproject.org/
code repositories for the project(s) associated with this inbox:
https://80x24.org/mirrors/git.git
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git