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

Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Sep 28, 2019, 23:35 UTC
Message-ID
<20190928233540.vsxhrik2vvgu4ahz@camp.crustytoothpaste.net>
In-Reply-To
<xmqq36ggj8ve.fsf@gitster-ct.c.googlers.com>
On 2019-09-28 at 23:31:33, Junio C Hamano wrote:
Show 20 quoted lines
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 
> > On 2019-09-07 at 17:26:53, Junio C Hamano wrote:
> >> * bc/object-id-part17 (2019-08-19) 26 commits
> >> ...
> >>  - builtin/replace: make hash size independent
> >> 
> >>  Preparation for SHA-256 upgrade continues.
> >> 
> >>  Looked mostly OK, with a possible update.
> >>  cf. <20190820223606.GJ365197@genre.crustytoothpaste.net>
> >
> > Just to update on the status of this, I wasn't planning on a reroll,
> > although I'm happy to do so if folks have feedback.  Opinions for or
> > against the current state are welcome.
> 
> I've already said that this looked mostly OK, and I think you and
> RRéne's "maybe adopt the use of oid_to_hex()s without using our own
> buffer" can come after the dust settles, so let's move this forward
> as-is.
That sounds like a fine way forward.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
Previous: Junio C HamanoNext: Martin Ågren
Message 8 of 16 in “What's cooking in git.git (Sep 2019, #01; Sat, 7)”
  1. Junio C HamanoSep 7, 2019
  2. Denton LiuSep 9, 2019
  3. Junio C HamanoSep 9, 2019
  4. Denton LiuSep 10, 2019
  5. brian m. carlsonSep 9, 2019
  6. Junio C HamanoSep 10, 2019
  7. Junio C HamanoSep 28, 2019
  8. brian m. carlsonSep 28, 2019
  9. Martin ÅgrenSep 10, 2019
  10. Josh SteadmonSep 10, 2019
  11. Matheus Tavares BernardinoSep 11, 2019
  12. pd/fetch-jobs, was Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)Johannes Schindelin, Sep 11, 2019
  13. Junio C HamanoSep 12, 2019
  14. Palmer DabbeltSep 14, 2019
  15. Junio C HamanoSep 16, 2019
  16. Palmer DabbeltSep 16, 2019

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.