[Libreoffice-qa] Using bibisect

Ilmari Lauhakangas ilmari.lauhakangas at libreoffice.org
Mon Nov 12 17:16:01 UTC 2018

Alex Kempshall kirjoitti 12.11.2018 klo 18.54:
> I'm sure I've done this before, but for the moment my brain's gone dead!
> If do
> $git status
> I get
>> On branch master
>> Your branch is up-to-date with 'origin/master'.
>> Untracked files:
>>   (use "git add <file>..." to include in what will be committed)
>>         instdir/user/
>> nothing added to commit but untracked files present (use "git add" to 
>> track)
> At the moment I'm not worried about the untracked files.

instdir/user is the user profile, don't worry about it.

> For bisect, on source code, I would normally do a git branch -a to see 
> what I've got and then start bisecting.
> git branch -a
> gives me
>> * master
>>   remotes/origin/HEAD -> origin/master
>>   remotes/origin/master
> I'm expecting a long list of branches which I could use to kick start my 
> good and bad bisect steps.

Branches are not used. Tagged commits are used, but usually only 
"oldest" and "latest" are tagged.
git tag -l
to list the tagged commits.

Using tags is not necessary. You can also just use commit hashes (of the 
bibisect repo commits.

The wiki article has some tips added this year, so do check it out: 


More information about the Libreoffice-qa mailing list