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
Samuel Lijin <sxlijin@gmail.com>
Date
Jun 1, 2017, 19:16 UTC
Message-ID
<CAJZjrdVS5e5udjLtZoZcTEUg8WGFPuaG+MB_enPJ9poti3LktQ@mail.gmail.com>
In-Reply-To
<alpine.DEB.2.21.1.1706012052480.3610@virtualbox>

On Thu, Jun 1, 2017 at 2:56 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 21 quoted lines
> Hi Junio,
>
> On Thu, 1 Jun 2017, Junio C Hamano wrote:
>
>> * dt/unpack-save-untracked-cache-extension (2017-05-20) 1 commit
>>   (merged to 'next' on 2017-05-23 at 3196d093d6)
>>  + unpack-trees: preserve index extensions
>>
>>  When "git checkout", "git merge", etc. manipulates the in-core
>>  index, various pieces of information in the index extensions are
>>  discarded from the original state, as it is usually not the case
>>  that they are kept up-to-date and in-sync with the operation on the
>>  main index.  The untracked cache extension is copied across these
>>  operations now, which would speed up "git status" (as long as the
>>  cache is properly invalidated).
>
> It was my understanding that Ben's analysis conclusively proved that the
> patch as well as the test are sound, and Dave agreed.
>
> 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).
> Ciao,
> Dscho
Previous: Johannes SchindelinNext: Junio C Hamano
Message 3 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.