* Andrew Pinski: > On Sun, May 19, 2019 at 12:54 PM Segher Boessenkool > <seg...@kernel.crashing.org> wrote:
>> Git can bisect automatically just fine, there is no upside to doing things >> manually. In git there are various handy ways of referring to commits; you >> can say master@{3 days ago} for example, or zut@{31} to get the 31st >> commit back on branch "zut", etc. See "man gitrevisions". > > Well one thing is if you have prebuilt cc1/cc1plus. So it is not > really doing a manual bisect per-say but rather it is doing a manual > bisect using prebuilt binaries and knowing which one comes before > which one. If GCC policy is to reject merge commits, a command similar to “git log --pretty=oneline | wc -l” gives something that is very much like a Subversion revision number, in the sense that it matches the commit ordering and that the assigned numbers remain stable over time. Thanks, Florian