On Thu, May 22, 2014 at 03:07:49PM -0400, David Turner wrote:
> On Thu, 2014-05-22 at 14:39 -0400, Jeff King wrote:
> > does show some improvement. Perhaps "git reset" is not writing out the
> > cache-tree extension?
> Yes, that seems to be exactly what is going on; the two indexes are
> identical up to the point where the TREE extension appears.
> Thanks for clearing that up!
> Do you think that this is a bug in git reset?
Possibly. There is a call to prime_cache_tree in builtin/reset.c, which
looks like it should trigger during a "mixed" or "hard" reset (and
without arguments, you should have a mixed reset). But it doesn't seem
to get called. I haven't traced it further.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html