From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org, Philipp Zabel <p.zabel@pengutronix.de>,
entwicklung@pengutronix.de
Subject: Re: git slow unless piped to cat
Date: Tue, 27 Aug 2019 12:56:38 +0200 [thread overview]
Message-ID: <20190827105638.2og6vwvqtzkkqn5p@pengutronix.de> (raw)
In-Reply-To: <20190827103309.GA8571@szeder.dev>
Hello,
On Tue, Aug 27, 2019 at 12:33:09PM +0200, SZEDER Gábor wrote:
> On Tue, Aug 27, 2019 at 12:04:27PM +0200, Uwe Kleine-König wrote:
> > I'm a bit surprised that the default for --decorate depends on the
> > output being a terminal.
>
> Decorations (and colors as well) are for humans, and humans read the
> terminal.
I agree for colors only. Changing the actually provided information
depending on output being a terminal is IMHO at least surprising.
> > Thanks for your help, I will think about what I want to do. Just using
> > --no-decorate will work, but isn't nice either. Will test if just
> > throwing away all those tags from linux-next will make this already
> > better.
>
> Note that you can disable decorations by setting the 'log.decorate'
> configuration variable to false.
Being able to configure --decorate-refs= and --decorate-refs-exclude= in
the config would be nice ...
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2019-08-27 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 8:15 git slow unless piped to cat Uwe Kleine-König
2019-08-27 8:41 ` SZEDER Gábor
2019-08-27 8:56 ` Uwe Kleine-König
2019-08-27 9:12 ` Philipp Zabel
2019-08-27 9:44 ` SZEDER Gábor
2019-08-27 10:04 ` Uwe Kleine-König
2019-08-27 10:33 ` SZEDER Gábor
2019-08-27 10:56 ` Uwe Kleine-König [this message]
2019-08-27 11:28 ` Michal Suchánek
2019-08-27 18:59 ` Jeff King
2019-08-27 21:32 ` Uwe Kleine-König
2019-08-27 21:38 ` Bryan Turner
2019-08-28 10:24 ` Uwe Kleine-König
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190827105638.2og6vwvqtzkkqn5p@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=entwicklung@pengutronix.de \
--cc=git@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=szeder.dev@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).