From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: "Jakub Narębski" <jnareb@gmail.com>, git <git@vger.kernel.org>,
"Abhishek Kumar" <abhishekkumar8222@gmail.com>,
"Derrick Stolee" <stolee@gmail.com>
Subject: Re: What's cooking in git.git (Sep 2020, #03; Wed, 9)
Date: Tue, 15 Sep 2020 15:32:16 -0700 [thread overview]
Message-ID: <xmqqr1r2y8lr.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200915214802.GB1741@nand.local> (Taylor Blau's message of "Tue, 15 Sep 2020 17:48:02 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> I completely agree with Junio's sentiment here. The overflow handling
> needs to exist no matter what, but let's remember what's common and what
> isn't.
>
> Since it's not common to be towards the end of even just the 32-bit
> range, let's "optimize" for that and store the fields as 32 bits wide.
Thanks. I realize I wasn't clear but that is what I meant. If we
need to deal with overflowing situation sensibly anyway, there may
not be much advantage in using 64-bit until year 2038.
next prev parent reply other threads:[~2020-09-15 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 22:32 What's cooking in git.git (Sep 2020, #03; Wed, 9) 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
2020-09-15 21:48 ` Taylor Blau
2020-09-15 22:32 ` Junio C Hamano [this message]
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=xmqqr1r2y8lr.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).