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 3, 2017, 00:26 UTC
Message-ID
<xmqqvaodx6g4.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<alpine.DEB.2.21.1.1706021211300.171564@virtualbox>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 18 quoted lines
> Hi Junio,
>
> On Fri, 2 Jun 2017, Junio C Hamano wrote:
>
>> 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.
>
> Okay. I never saw any "Will merge to" message, so I got worried.
Well, I cannot quite help if you are not reading them ;-)

Issue #06 of May marked it to be merged to 'next': https://public-inbox.org/git/<xmqqo9ulo1yn.fsf@gitster.mtv.corp.google.com>

Issue #07 of May marked it for 'master': https://public-inbox.org/git/<xmqqwp98j8q2.fsf@gitster.mtv.corp.google.com>

Issue #08 of May kept it (i.e. no issues discovered in the meantime): https://public-inbox.org/git/<xmqq1sr889lb.fsf@gitster.mtv.corp.google.com>

Issue #01 of June reports it in 'master': https://public-inbox.org/git/<xmqqshjk5ezb.fsf@gitster.mtv.corp.google.com>

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 6 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.