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

Re: What's cooking in git.git (Mar 2015, #07; Fri, 20)

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 21, 2015, 03:20 UTC
Message-ID
<xmqqegojc9yd.fsf@gitster.dls.corp.google.com>
In-Reply-To
<423416FC-1048-4D3A-B997-F1F796627242@gmail.com>
"Kyle J. McKay" <mackyle@gmail.com> writes:
>> Will cook in 'next'.
>
> Has this been merged to 'next'?  Even fetching
> github.com/gitster/git.git I'm only seeing it in pu:
That was a short-hand for "will merge and cook in 'next'" ;-)

I had an impression that the series may see at least one reroll to polish it further before it gets ready for 'next', as I only saw discussions on the tangent (e.g. possible futures) and didn't see serious reviews of the code that we will actually be using.

Previous: Kyle J. McKayNext: brian m. carlson
Message 5 of 7 in “What's cooking in git.git (Mar 2015, #07; Fri, 20)”
  1. Junio C HamanoMar 20, 2015
  2. Kyle J. McKayMar 20, 2015
  3. Stefan BellerMar 20, 2015
  4. Kyle J. McKayMar 21, 2015
  5. Junio C HamanoMar 21, 2015
  6. brian m. carlsonMar 21, 2015
  7. Junio C HamanoMar 22, 2015

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.