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

Re: What's cooking in git.git (Sep 2020, #03; Wed, 9)

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 15, 2020, 22:32 UTC
Message-ID
<xmqqr1r2y8lr.fsf@gitster.c.googlers.com>
In-Reply-To
<20200915214802.GB1741@nand.local>
Taylor Blau <me@ttaylorr.com> writes:
Show 6 quoted lines
> 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.

Previous: Taylor BlauNext: Jakub Narębski
Message 12 of 13 in “What's cooking in git.git (Sep 2020, #03; Wed, 9)”
  1. Junio C HamanoSep 9, 2020
  2. Eric SunshineSep 9, 2020
  3. Junio C HamanoSep 10, 2020
  4. Eric SunshineSep 15, 2020
  5. Junio C HamanoSep 15, 2020
  6. Jakub NarębskiSep 15, 2020
  7. Taylor BlauSep 15, 2020
  8. Junio C HamanoSep 15, 2020
  9. Jakub NarębskiSep 15, 2020
  10. Junio C HamanoSep 15, 2020
  11. Taylor BlauSep 15, 2020
  12. Junio C HamanoSep 15, 2020
  13. Jakub NarębskiSep 15, 2020

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.