Bisecting using git

[Jan Mulder]

On 20-10-17 12:07, Willem Ferguson wrote:
> On 20/10/2017 11:08, Jan Mulder wrote:
>> On 20-10-17 10:48, Willem Ferguson wrote:
>>> When bisecting, what type of version/commit number is used to refer 
>>> to specific commits?
>>
>> Did you read https://git-scm.com/docs/git-bisect ?
>>
>> you can use all kinds of references to a commit. Its SHA, a label 
>> attached to it. And probably more, that I never used.
>>
>> --jan
>>
> Thank you, Jan.
> 
> willem at FINS:~/src/subsurface$ git bisect start
> willem at FINS:~/src/subsurface$ git bisect bad
> willem at FINS:~/src/subsurface$ git bisect good 4.6.4-1003
> fatal: Needed a single revision
> Bad rev input: 4.6.4-1003
> willem at FINS:~/src/subsurface$
> 
> I have no way of defining 4.6.4.1003 better. I need a better way to 
> specify a reference to  a commit and selecting Help->About Subsurface 
> does not give more info.

Not sure I fully understand your issue. For example, my current build 
(-1032) shows in the About screen: .... 4.6.4-1032-g46d0af4849d2

The g46d0af4849d2 part is the SHA (without the g), so the SHA you can 
use in a bisect is 46d0af4849d2 (and this a SHA from a local commit from 
me on top of the current master, so this one is not in the official repo).

--jan