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

Re: What's cooking in git.git (Sep 2019, #02; Wed, 18)

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Sep 18, 2019, 22:37 UTC
Message-ID
<20190918223741.79215-1-jonathantanmy@google.com>
In-Reply-To
<xmqqy2yl44lw.fsf@gitster-ct.c.googlers.com>
Show 8 quoted lines
> * jt/cache-tree-avoid-lazy-fetch-during-merge (2019-09-09) 1 commit
>  - cache-tree: do not lazy-fetch tentative tree
> 
>  The cache-tree code has been taught to be less aggressive in
>  attempting to see if a tree object it computed already exists in
>  the repository.
> 
>  Waiting for a response to an updated log message.
I've responded here:
https://public-inbox.org/git/20190910181534.134890-1-jonathantanmy@google.com/

Let me know if this response is sufficient or if you were expecting something else.

Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 13 in “What's cooking in git.git (Sep 2019, #02; Wed, 18)”
  1. Junio C HamanoSep 18, 2019
  2. Jonathan TanSep 18, 2019
  3. Junio C HamanoSep 20, 2019
  4. Martin ÅgrenSep 19, 2019
  5. Junio C HamanoSep 20, 2019
  6. Thomas GummererSep 19, 2019
  7. Junio C HamanoSep 20, 2019
  8. Taylor BlauSep 20, 2019
  9. Junio C HamanoSep 20, 2019
  10. git-gui contributions, was Re: What's cooking in git.git (Sep 2019, #02; Wed, 18)Johannes Schindelin, Sep 23, 2019
  11. Pratyush YadavSep 24, 2019
  12. Johannes SchindelinSep 26, 2019
  13. Pratyush YadavSep 26, 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.