On 6/1/2018 7:15 PM, Junio C Hamano wrote:
Derrick Stolee writes:
A recently added "commit-graph" datafile has learned to store
pre-computed generation numbers to speed up the decisions to stop
history traversal.
Will cook in 'next'.
On Wednesday, these were marked as "Will merge
Derrick Stolee writes:
>> A recently added "commit-graph" datafile has learned to store
>> pre-computed generation numbers to speed up the decisions to stop
>> history traversal.
>>
>> Will cook in 'next'.
>
> On Wednesday, these were marked as "Will merge to 'master'" What changed?
> * jm/cache-entry-from-mem-pool (2018-05-24) 7 commits
> - block alloc: add validations around cache_entry lifecyle
> - block alloc: allocate cache entries from mem_pool
> - mem-pool: fill out functionality
> - mem-pool: add lifecycle management functions
> - mem-pool: only search head block
On 6/1/2018 3:21 AM, Junio C Hamano wrote:
* ds/commit-graph-lockfile-fix (2018-05-22) 1 commit
(merged to 'next' on 2018-05-24 at 3d12a02b0c)
+ commit-graph: fix UX issue when .lock file exists
(this branch is used by ds/commit-graph-fsck; uses ds/generation-numbers.)
Update to
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
You can find the changes
5 matches
Mail list logo
