Hi all
I'm more of a bisect person, but towards the end of last week I did a
bibisect looking for a regression I've encountered. Will post details
later today.
As far as my understanding goes I can use bibisect to identify which day
the commit that caused the regression was made. How do I th
git://dev-downloads.libreoffice.org/lo-linux-dbgutil-daily-till53.git
So I'm covered from May 2016 through to May 2018.
Alex
On 11/06/18 15:11, Xisco Fauli wrote:
Hello Alex,
El 11/06/18 a les 14:53, Alex Kempshall ha escrit:
Hi all
I'm more of a bisect person, but towards the end of last w
20#c3
Just want to know how you got from my bibisect.
Alex
On 12/06/18 11:24, Alex Kempshall wrote:
I'm using the dbgutil series. Storage is cheap so I've cloned
git://dev-downloads.libreoffice.org/lo-linux-dbgutil-daily-till61.git
git://dev-downloads.libreoffice.org/lo-linux-dbgutil-d
Hi Xisco
I've move to the max series.
Thanks
Alex
On 20/06/18 14:34, Xisco Fauli wrote:
Hello Alex,
El 20/06/18 a les 13:47, Alex Kempshall ha escrit:
Hi Xisco
Still don't understand what the technique is to get from a bibisect
log to a bisect log.
If you remember I iden
Hi Xisco
I would have liked to have listened in on tomorrows meeting,
unfortunately I have to be elsewhere.
Back in 2016 Buovjaga wrote this to me
mailmerge testing is very valuable as it is a complex feature and typically not
many QA members like to tackle it.
On IRC, there are usually peo
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
x
On 12/11/2018 17:16, Ilmari Lauhakangas wrote:
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'.
U
