From: Jacob MacDonald <jaccarmac@gmail.com>
To: 54033@debbugs.gnu.org
Subject: bug#54033: Fwd: bug#54033: Calibre's ebook-viewer only shows white-on-white or dark-on-dark.
Date: Sat, 19 Feb 2022 23:05:59 -0600 [thread overview]
Message-ID: <CACy6W0AT1TPUGT=6OC6mQmRt20AxdJRXwoDJoS9TEHPwcEmRyw@mail.gmail.com> (raw)
In-Reply-To: <CACy6W0AaVRTrrduJPi_ZCWyoMK8KoKDbEyVWEFQ2xtgZxRMgQg@mail.gmail.com>
---------- Forwarded message ---------
From: Jacob MacDonald <jaccarmac@gmail.com>
Date: Sat, Feb 19, 2022 at 2:13 PM
Subject: Re: bug#54033: Calibre's ebook-viewer only shows
white-on-white or dark-on-dark.
To: Leo Famulari <leo@famulari.name>
On Fri, Feb 18, 2022 at 10:28 PM Leo Famulari <leo@famulari.name> wrote:
> Can you keep trying and let us know the results?
As luck would have it, bisecting the smaller set gives me
6dffced09ecda024e0884e352778c221ad066fd6 as the first bad commit. And
that's the big merge. I'm guessing that the next step is to bisect
some subset of what used to be core-updates-frozen, but I have not
gotten there yet.
> In general, when bisecting a range of commits that includes merge commits, you should use the --first-parent option
Thanks again for the bisect help. That made the search much narrower
and the builds far easier.
Jacob.
next prev parent reply other threads:[~2022-02-20 5:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 7:05 bug#54033: Calibre's ebook-viewer only shows white-on-white or dark-on-dark Jacob MacDonald
2022-02-17 23:41 ` Leo Famulari
2022-02-20 3:39 ` Jacob MacDonald
2022-02-20 4:33 ` Leo Famulari
[not found] ` <CACy6W0Aj8CAnc47p_R5rHw2d3vNaFEoKaxhRRJRXyhVQekcR7w@mail.gmail.com>
2022-02-20 5:05 ` bug#54033: Fwd: " Jacob MacDonald
[not found] ` <18be745d-10bf-4be9-bef3-c88cc88d9554@www.fastmail.com>
2022-02-20 5:05 ` Jacob MacDonald
[not found] ` <CACy6W0AaVRTrrduJPi_ZCWyoMK8KoKDbEyVWEFQ2xtgZxRMgQg@mail.gmail.com>
2022-02-20 5:05 ` Jacob MacDonald [this message]
2022-02-21 3:46 ` Jacob MacDonald
2022-02-21 6:00 ` Jacob MacDonald
2022-02-22 4:51 ` Jacob MacDonald
2022-03-04 4:07 ` Jacob MacDonald
2022-03-04 13:19 ` Leo Famulari
2022-03-04 18:19 ` Jacob MacDonald
2022-03-04 14:07 ` Guillaume Le Vaillant
2022-03-04 20:27 ` bdju via Bug reports for GNU Guix
2022-03-08 14:52 ` Guillaume Le Vaillant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACy6W0AT1TPUGT=6OC6mQmRt20AxdJRXwoDJoS9TEHPwcEmRyw@mail.gmail.com' \
--to=jaccarmac@gmail.com \
--cc=54033@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.