From: patchwork-bot+netdevbpf@kernel.org
To: Ben Hutchings <benh@debian.org>
Cc: netdev@vger.kernel.org, 1088739@bugs.debian.org
Subject: Re: [PATCH iproute2 0/2] Improve coloured text readability
Date: Sun, 06 Apr 2025 17:00:31 +0000 [thread overview]
Message-ID: <174395883101.3915601.12663175368150870282.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Z-QKNa7_nHKoh9Gl@decadent.org.uk>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 26 Mar 2025 15:07:49 +0100 you wrote:
> Currently coloured text output isn't very readable in GNOME Terminal
> or xterm with a dark background:
>
> - These terminals don't set $COLORFGBG, so we end up using the
> light-background palette.
>
> - The standard (dark) blue is also too close to black in their default
> dark palettes.
>
> [...]
Here is the summary with links:
- [iproute2,1/2] color: Assume background is dark if unknown
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=cc0f1109d286
- [iproute2,2/2] color: Do not use dark blue in dark-background palette
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=46a4659313c2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-04-06 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 14:07 [PATCH iproute2 0/2] Improve coloured text readability Ben Hutchings
2025-03-26 14:08 ` [PATCH iproute2 1/2] color: Assume background is dark if unknown Ben Hutchings
2025-03-26 14:08 ` [PATCH iproute2 2/2] color: Do not use dark blue in dark-background palette Ben Hutchings
2025-04-06 17:00 ` patchwork-bot+netdevbpf [this message]
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=174395883101.3915601.12663175368150870282.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=1088739@bugs.debian.org \
--cc=benh@debian.org \
--cc=netdev@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).