Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread Junio C Hamano
David Turner writes: > On Tue, 2015-07-28 at 13:47 -0700, Junio C Hamano wrote: >> David Turner writes: >> >> > When we unpack trees into an existing index, we discard the old index >> > and replace it with the new, merged index. Ensure that this index has >> > its cache-tree populated. This

Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread David Turner
On Tue, 2015-07-28 at 13:47 -0700, Junio C Hamano wrote: > David Turner writes: > > > When we unpack trees into an existing index, we discard the old index > > and replace it with the new, merged index. Ensure that this index has > > its cache-tree populated. This will make subsequent git statu

Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread Junio C Hamano
David Turner writes: > Git checkout $branch already populates the cache-tree; this is due to > patches I added last year: > > commit aecf567cbfb6ab46e82f7f5df36fb6a2dd5bee69 Heh, our mails crossed ;-) Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a mes

Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread Junio C Hamano
David Turner writes: > When we unpack trees into an existing index, we discard the old index > and replace it with the new, merged index. Ensure that this index has > its cache-tree populated. This will make subsequent git status and > commit commands faster. > > Signed-off-by: David Turner >

Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread David Turner
On Tue, 2015-07-28 at 13:04 -0700, Junio C Hamano wrote: > Junio C Hamano writes: > > > David Turner writes: > > > >> The work done to produce the cache-tree is work that the commit would > >> otherwise have to do. So we're spending extra time in one place to > >> eliminate that work in a diffe

Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread Junio C Hamano
Junio C Hamano writes: > David Turner writes: > >> The work done to produce the cache-tree is work that the commit would >> otherwise have to do. So we're spending extra time in one place to >> eliminate that work in a different place. > > Good point. Thanks. Hmm, I forgot about another codep

Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread Junio C Hamano
David Turner writes: > The work done to produce the cache-tree is work that the commit would > otherwise have to do. So we're spending extra time in one place to > eliminate that work in a different place. Good point. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in

Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread David Turner
On Tue, 2015-07-28 at 12:50 -0700, Junio C Hamano wrote: > David Turner writes: > > > When we unpack trees into an existing index, we discard the old index > > and replace it with the new, merged index. Ensure that this index has > > its cache-tree populated. This will make subsequent git statu

Re: [PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread Junio C Hamano
David Turner writes: > When we unpack trees into an existing index, we discard the old index > and replace it with the new, merged index. Ensure that this index has > its cache-tree populated. This will make subsequent git status and > commit commands faster. Wouldn't it make repeated calls to

[PATCH] cache-tree: populate cache-tree on successful merge

2015-07-28 Thread David Turner
When we unpack trees into an existing index, we discard the old index and replace it with the new, merged index. Ensure that this index has its cache-tree populated. This will make subsequent git status and commit commands faster. Signed-off-by: David Turner Signed-off-by: Brian Degenhardt ---