Re: [PATCH v2 2/2] cache-tree: do not generate empty trees as a result of all i-t-a subentries
From: Junio C Hamano <hidden>
Date: 2016-07-07 18:54:16
Possibly related (same subject, not in this thread)
- 2016-07-08 · Re: [PATCH v2 2/2] cache-tree: do not generate empty trees as a result of all i-t-a subentries · Junio C Hamano <hidden>
- 2016-07-08 · Re: [PATCH v2 2/2] cache-tree: do not generate empty trees as a result of all i-t-a subentries · Duy Nguyen <hidden>
- 2016-07-08 · Re: [PATCH v2 2/2] cache-tree: do not generate empty trees as a result of all i-t-a subentries · Junio C Hamano <hidden>
- 2016-07-07 · Re: [PATCH v2 2/2] cache-tree: do not generate empty trees as a result of all i-t-a subentries · Duy Nguyen <hidden>
- 2016-07-06 · Re: [PATCH v2 2/2] cache-tree: do not generate empty trees as a result of all i-t-a subentries · Junio C Hamano <hidden>
Duy Nguyen [off-list ref] writes:
I'll deal with that separately. Let's focus on cache-tree only this time. So how about this on top?
I was hoping that you would limit the scope of the test to check if write-tree does the right thing. i.e. not test "git commit", but test "git write-tree".