All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, David Turner <dturner@twosigma.com>,
	Ben Peart <benpeart@microsoft.com>
Subject: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)
Date: Thu, 1 Jun 2017 20:56:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1.1706012052480.3610@virtualbox> (raw)
In-Reply-To: <xmqqshjk5ezb.fsf@gitster.mtv.corp.google.com>

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`?

Ciao,
Dscho

  reply	other threads:[~2017-06-01 18:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01  7:44 What's cooking in git.git (Jun 2017, #01; Thu, 1) Junio C Hamano
2017-06-01 18:56 ` Johannes Schindelin [this message]
2017-06-01 19:16   ` preserve untracked cache, was " Samuel Lijin
2017-06-01 23:19     ` Junio C Hamano
2017-06-02 10:11       ` Johannes Schindelin
2017-06-03  0:26         ` Junio C Hamano
2017-06-15 10:34           ` Johannes Schindelin
2017-06-01 21:06 ` Johannes Sixt
2017-06-01 23:14   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1.1706012052480.3610@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=benpeart@microsoft.com \
    --cc=dturner@twosigma.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.