From: Jani Nikula <jani.nikula@linux.intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Knop, Ryszard" <ryszard.knop@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"rk@dragonic.eu" <rk@dragonic.eu>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
"daniel@fooishbar.org" <daniel@fooishbar.org>,
Sima Vetter <sima@ffwll.ch>
Subject: Re: Discussion: Moving away from Patchwork for Intel i915/Xe CI
Date: Fri, 07 Mar 2025 11:23:09 +0200 [thread overview]
Message-ID: <87bjudi48y.fsf@intel.com> (raw)
In-Reply-To: <20250306-guillemot-of-nonstop-honeydew-aed30a@lemur>
On Thu, 06 Mar 2025, Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Thu, Mar 06, 2025 at 12:42:07PM +0200, Jani Nikula wrote:
>> I haven't had the time to dig into b4 source on this, but it would be
>> great if it could automatically detect whether sending colors is the
>> right thing to do or not. Basically only emit color codes to interactive
>> terminals, unless forced also for pipes.
>
> Yes, it should do that automatically. Please send a bug report to
> tools@kernel.org and I'll work an automated switch to "simple" attestation
> marks when we don't have a terminal.
Done. Link for posterity [1].
BR,
Jani.
[1] https://lore.kernel.org/r/87ecz9i4eo.fsf@intel.com
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-03-07 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 16:51 Discussion: Moving away from Patchwork for Intel i915/Xe CI Knop, Ryszard
2025-03-05 17:30 ` Lucas De Marchi
2025-03-05 17:52 ` Jani Nikula
2025-03-05 19:33 ` Konstantin Ryabitsev
2025-03-06 10:42 ` Jani Nikula
2025-03-06 16:44 ` Konstantin Ryabitsev
2025-03-07 9:23 ` Jani Nikula [this message]
2025-03-05 19:54 ` Ryszard Knop
2025-03-06 10:48 ` Jani Nikula
2025-03-05 20:32 ` Lucas De Marchi
2025-03-06 8:20 ` Jani Nikula
2025-03-13 10:22 ` Jani Nikula
2025-03-13 10:40 ` Jani Nikula
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=87bjudi48y.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel@fooishbar.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=konstantin@linuxfoundation.org \
--cc=lucas.demarchi@intel.com \
--cc=rk@dragonic.eu \
--cc=ryszard.knop@intel.com \
--cc=sima@ffwll.ch \
/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 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.