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

Re: What's cooking in git.git (Feb 2022, #03; Sat, 12)

From
Chen BoJun <bojun.cbj@gmail.com>
Date
Feb 15, 2022, 02:09 UTC
Message-ID
<20220215020923.38168-1-bojun.cbj@gmail.com>
In-Reply-To
<xmqq5ypj6rw6.fsf@gitster.g>
Show 11 quoted lines
> * cb/clear-quarantine-early-on-all-ref-update-errors (2022-02-01) 1 commit
>  - receive-pack: purge temporary data if no command is ready to run
>
>  Check if "receive-pack" will do any ref updates (various conditions
>  could reject a push) before received objects are taken out of the
>  temporary directory used for quarantine purposes, so that a push
>  that is known-to-fail will not leave crufts that a future "gc"
>  needs to clean up.
>
>  Will merge to 'next'.
>  source: <20220129063538.24038-1-bojun.cbj@gmail.com>

I noticed that the merged patch was v2, not v3 which I sent last week. Apart from a more complete commit message, there is no change in patch v3. So merge patch v2 is OK.

Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 6 in “What's cooking in git.git (Feb 2022, #03; Sat, 12)”
  1. Junio C HamanoFeb 13, 2022
  2. Jonathan TanFeb 14, 2022
  3. Junio C HamanoFeb 14, 2022
  4. Chen BoJunFeb 15, 2022
  5. Junio C HamanoFeb 15, 2022
  6. js/use-builtin-add-i (was Re: What's cooking in git.git (Feb 2022, #03; Sat, 12))Phillip Wood, Feb 15, 2022

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.