Alex Kempshall kirjoitti 12.11.2018 klo 19.42:
Branches are not used. Tagged commits are used, but usually only
"oldest" and "latest" are tagged.
So this is maybe why I did this the last time I did a bibisect
git checkout f69ad1e0f0cfcfc6488e3739c4ef7efcc1445b72
git bisect start
git bisect go
Ilmari
Thanks for the reply where you wrote
Branches are not used. Tagged commits are used, but usually only
"oldest" and "latest" are tagged.
So this is maybe why I did this the last time I did a bibisect
git checkout f69ad1e0f0cfcfc6488e3739c4ef7efcc1445b72
git bisect start
git bisect goo
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 ..." to include in what will be committed)
I'm sure I've done this before, but for the moment my brain's gone dead!
I've changed to what I regard as my bibisect working directory and done
$git pull
Seemed to behave as I expected. I've subsequently done another pull and
the results the second time are again to me as expected -
instd
