From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] [PATCH 1/1] Dockerfile: enable colored output
Date: Sun, 6 Oct 2019 12:35:49 -0400 [thread overview]
Message-ID: <20191006163549.GV15735@bill-the-cat> (raw)
In-Reply-To: <20191006151202.754-1-xypron.glpk@gmx.de>
On Sun, Oct 06, 2019 at 05:12:02PM +0200, Heinrich Schuchardt wrote:
> Set environment variables needed for colored output.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> Hello Tom,
>
> I do not have my own Gitlab to test this. But we should get a more legible
> output with these variables set.
You can build your own images, push those and have your branch use them,
as that's how I test my own Docker changes. If you can't easily do that
however, I'll give this a spin. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191006/1e27fb62/attachment.sig>
prev parent reply other threads:[~2019-10-06 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 15:12 [U-Boot] [RFC] [PATCH 1/1] Dockerfile: enable colored output Heinrich Schuchardt
2019-10-06 16:35 ` Tom Rini [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=20191006163549.GV15735@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.