Re: Bisecting using git

2017-10-20 Thread Linus Torvalds
On Fri, Oct 20, 2017 at 6:07 AM, Willem Ferguson wrote: > > willem@FINS:~/src/subsurface$ git bisect good 4.6.4-1003 > fatal: Needed a single revision > Bad rev input: 4.6.4-1003 > > I have no way of defining 4.6.4.1003 better. Yeah, the subsurface package naming

Re: Bisecting using git

2017-10-20 Thread 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

Re: Bisecting using git

2017-10-20 Thread Willem Ferguson
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

Re: Bisecting using git

2017-10-20 Thread Jan Mulder
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

Bisecting using git

2017-10-20 Thread Willem Ferguson
When bisecting, what type of version/commit number is used to refer to specific commits? Kind regards, willem -- This message and attachments are subject to a disclaimer. Please refer to http://upnet.up.ac.za/services/it/documentation/docs/004167.pdf for full details.