Actually, one case that I may not have considered properly is a commit
near the head that has no parents.
git-rev-list --parents v2.6.12-rc6-astorm1 ^v2.6.12-rc6
should tell you if this case exists. Ideally such a case should not
occur, but that isn't a logical certainity, so I should handle it
better than I currently do.
Please let me know if this may explain your case.
Regards,
jon.
Jon Seymour wrote:
Actually, one case that I may not have considered properly is a commit
near the head that has no parents.
git-rev-list --parents v2.6.12-rc6-astorm1 ^v2.6.12-rc6
should tell you if this case exists. Ideally such a case should not
occur, but that isn't a logical certainity, so I should handle it
better than I currently do.
Please let me know if this may explain your case.
This just threw tons of SHA1 hashes at me without complaining.
I've also tried git-rev-list HEAD >/dev/null without any chage whatsoever.
The tree is not secret, You can try (very slow) rsync at:
rsync://astralstorm.servegame.com/linux-2.6-astorm
Just update latest linux-2.6 with it to save time.
(mine is up to commit 1d6757fbff5bc86e94e59ab0d7bdd7e71351d839)
AstralStorm
Ok, I reproduced exponential behaviour when a commit with no parents
is merged near the head of the kernel and a ^ argument is specified.
Fortunately a work-around is a one line change - a patch will be
forthcoming shortly.
The workaround will still require a full-graph scan but that is linear
rather than
exponential so is tolerable.
A better solution which will not require a full-graph scan will be
delivered in a future
patch.
Thanks for the report.
jon.