Yuya Nishihara 38e7eff09f index: merge overlapped generation ranges to be enqueued ... Before, the number of the generations to track would increase at each merge point. This was really bad for queries like ':@--' in merge-heavy history, but I didn't notice the problem because ancestors query is lazy and the default log template is slow. Since I'm going to reuse RevWalk for 'roots++:' queries, which can't be lazy, I need to fix this problem first. As we don't have a revset expression to specify exact generation range, gen.end is initialized to either 1 or close to u32::MAX. So, this change means long-lived generation ranges will eventually be merged into one.		2023-04-27 08:18:47 +09:00
..
bench-revsets-git.txt	index: merge overlapped generation ranges to be enqueued	2023-04-27 08:18:47 +09:00
fake-diff-editor.rs
fake-editor.rs