Re: final git bisect step leads to: "fatal: you want to use way too much memory"

Jeff King writes: > Interesting. But `git show` on the commit in question (f216419e5) does > not have any problems. It looks like bisect's internal "show the commit" > code does not properly call setup_revisions() to finalize the "struct > rev_info". That leaves the expand_tabs_in_log flag as "-1

Re: final git bisect step leads to: "fatal: you want to use way too much memory"

On Thu, Jun 16, 2016 at 03:29:52PM +0200, Markus Trippelsdorf wrote: > On 2016.06.16 at 14:53 +0200, Markus Trippelsdorf wrote: > > markus@x4 gcc % git bisect good > > f216419e5c4c41df70dbe00a6ea1faea46484dc8 is the first bad commit > > commit f216419e5c4c41df70dbe00a6ea1faea46484dc8 > > fatal: yo

Re: final git bisect step leads to: "fatal: you want to use way too much memory"

On 2016.06.16 at 14:53 +0200, Markus Trippelsdorf wrote: > markus@x4 gcc % git bisect good > f216419e5c4c41df70dbe00a6ea1faea46484dc8 is the first bad commit > commit f216419e5c4c41df70dbe00a6ea1faea46484dc8 > fatal: you want to use way too much memory > markus@x4 gcc % The issue started with: c

Re: final git bisect step leads to: "fatal: you want to use way too much memory"

On 2016.06.16 at 14:53 +0200, Markus Trippelsdorf wrote: > To reproduce the issue, just run: Forget to mention: markus@x4 ~ % git --version git version 2.9.0 git-2.8.4 is fine. -- Markus -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vg

final git bisect step leads to: "fatal: you want to use way too much memory"

To reproduce the issue, just run: markus@x4 ~ % git clone git://gcc.gnu.org/git/gcc.git markus@x4 gcc % git checkout -b gcc-6 origin/gcc-6-branch markus@x4 gcc % git bisect bad 23240454adf1 You need to start by "git bisect start" Do you want me to do it for you [Y/n]? y markus@x4 gcc % git bisect