2 messages, 2 authors, 2016-06-15 · open the first message on its own page
From: Radoslaw Szkodzinski <hidden>
Date: 2016-06-15 22:41:59
I've got a Linux git tree with some merges and some other commits interwined. I want to print all my changes in merge order, so I do: git-rev-list --pretty --merge-order v2.6.12-rc6-astorm1 ^v2.6.12-rc6 It prints the first 3 commits (linear), but then hangs, eating all available CPU. Without --merge-order it works fine, but obviously lists the commits by parent. AstralStorm
From: Jon Seymour <hidden>
Date: 2016-06-15 22:41:59
On 6/8/05, Radoslaw Szkodzinski [off-list ref] wrote:
I've got a Linux git tree with some merges and some other commits interwined. I want to print all my changes in merge order, so I do: git-rev-list --pretty --merge-order v2.6.12-rc6-astorm1 ^v2.6.12-rc6 It prints the first 3 commits (linear), but then hangs, eating all available CPU. Without --merge-order it works fine, but obviously lists the commits by parent.
Can you git-rev-list >/dev/null without arguments, then do a
git-rev-list --pretty --merge-order again and see it works any better?
If it still doesn't work, can you send me the output of:
git-rev-list --parents v2.6.12-rc6-astorm1 ^v2.6.12-rc6
I may then need to request a tarball of the related git objects so
that I can reproduce the problem on my end, but I'll send you the list
I need to see.
Regards,
jon.