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

Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 1, 2017, 23:19 UTC
Message-ID
<xmqqfufj47oz.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAJZjrdVS5e5udjLtZoZcTEUg8WGFPuaG+MB_enPJ9poti3LktQ@mail.gmail.com>
Samuel Lijin <sxlijin@gmail.com> writes:
>> What is holding this topic up? Anything Ben or I can do to move this
>> closer to `next` or even `master`?
>
> It's in `next` right now (3196d093d6).
Thanks for pinging and checking ;-)

I think the topic was merged to 'next' on the 23rd of last month and graduated to 'master' in the past few days, together with other topics.

Previous: Samuel LijinNext: Johannes Schindelin
Message 4 of 9 in “What's cooking in git.git (Jun 2017, #01; Thu, 1)”
  1. Junio C HamanoJun 1, 2017
  2. preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)Johannes Schindelin, Jun 1, 2017
  3. Samuel LijinJun 1, 2017
  4. Junio C HamanoJun 1, 2017
  5. Johannes SchindelinJun 2, 2017
  6. Junio C HamanoJun 3, 2017
  7. Johannes SchindelinJun 15, 2017
  8. Johannes SixtJun 1, 2017
  9. Junio C HamanoJun 1, 2017

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.