From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jose Wielandt <jose.wielandt@timining.com>
Cc: Fabian Stelzer <fs@gigacodes.de>, git <git@vger.kernel.org>
Subject: Re: Please, paint new branch errors in RED (or any visible color)
Date: Sat, 11 Dec 2021 03:30:00 +0100 [thread overview]
Message-ID: <211211.86a6h7c1mq.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <CAJrA3nKbUK=_5d5KTCDehrfge4y1aB9YGsFwQYNzUDWGcfog4w@mail.gmail.com>
On Fri, Dec 10 2021, Jose Wielandt wrote:
> Yes, I git switch has the same behavior.
> I also agree that add hints could be a good idea.
I'll pick up this topic.
I have some patches I'm trickling in to improve the general UX of these
fatal/error/warning/hint etc. messages, one part of that is trying to
get this RFC series in incrementally (some patches are already on-list:
https://lore.kernel.org/git/RFC-cover-00.21-00000000000-20211115T220831Z-avarab@gmail.com/
Adding color to the output would be relatively easy. I'll get to it, and
feel free to send me a reminder in some months (which is realistically
when you'd see it in a release) if you don't see it.
Thanks for the suggestion, & for caring about git's UX.
next prev parent reply other threads:[~2021-12-11 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 11:36 Please, paint new branch errors in RED (or any visible color) Jose Wielandt
2021-12-10 16:32 ` Ævar Arnfjörð Bjarmason
2021-12-10 16:42 ` Fabian Stelzer
2021-12-10 19:09 ` Jose Wielandt
2021-12-11 2:30 ` Ævar Arnfjörð Bjarmason [this message]
2021-12-12 18:38 ` Junio C Hamano
2021-12-12 19:01 ` Ævar Arnfjörð Bjarmason
2021-12-12 22:27 ` Eric Sunshine
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=211211.86a6h7c1mq.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=fs@gigacodes.de \
--cc=git@vger.kernel.org \
--cc=jose.wielandt@timining.com \
/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.