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

Re: What's cooking in git.git (Feb 2016, #04; Fri, 12)

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 15, 2016, 04:50 UTC
Message-ID
<xmqqy4amr2z4.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<56C07182.1040804@web.de>
Torsten Bögershausen <tboegi@web.de> writes:
Show 6 quoted lines
>> * tb/conversion (2016-02-10) 6 commits
>>   (merged to 'next' on 2016-02-12 at 6faf27b)
> Could we keep it in next for a while ?
>
> I found issues that needs to be fixed before going to master,
> updates follow soonish.

Hmph, I somehow thought that everything was a no-op clean-up. Any regressions I failed to spot?

Previous: Torsten BögershausenNext: Torsten Bögershausen
Message 3 of 5 in “What's cooking in git.git (Feb 2016, #04; Fri, 12)”
  1. Junio C HamanoFeb 12, 2016
  2. Torsten BögershausenFeb 14, 2016
  3. Junio C HamanoFeb 15, 2016
  4. Torsten BögershausenFeb 15, 2016
  5. Junio C HamanoFeb 15, 2016

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.