From: "Jakub Narębski" <jnareb@gmail.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Terrible bad performance for it blame --date=iso -C
Date: Mon, 3 Apr 2017 17:16:01 +0200 [thread overview]
Message-ID: <0ccc5cab-26b7-4b02-b964-452b61e92579@gmail.com> (raw)
In-Reply-To: <20170403105641.16912-1-szeder.dev@gmail.com>
W dniu 03.04.2017 o 12:56, SZEDER Gábor pisze:
> Ulrich Windl wrote:
>> In the other case (for the user bored of waiting seeking for some
>> entertainment ;-)) a "-v (verbose) option could be useful. Or at the
>> very least: If git is expecting that some operation will take (or
>> already did take) a lot of time, give some message explaining why it
>> is taking a lot of time, and maybe how to avoid that.
>
> It already does so by default since v2.8.0, see aba37f495 (blame: add
> support for --[no-]progress option, 2015-12-12).
>
> $ time git blame sha1_file.c |wc -l
> 4026
>
> real 0m1.744s
> user 0m1.672s
> sys 0m0.068s
> $ time git blame -C -C sha1_file.c |wc -l
> Blaming lines: 100% (4026/4026), done.
> 4026
>
> real 0m3.832s
> user 0m3.716s
> sys 0m0.112s
>
> However, after a short peek at that commit, it only displays progress
> by default when stderr is a terminal, which might not be the case when
> invoked from emacs.
Emacs (magit?) should use `git blame --porcelain`, and do its own
progress report, just like 'git gui blame' and incremental blame mode
of gitweb.
Actually... there already is git-blamed - Minor mode for incremental
blame for Git, and mo-git-blame - An interactive, iterative 'git blame'
mode for Emacs, both available on ELPA (Emacs Lisp Package Archive).
HTH
--
Jakub Narębski
next prev parent reply other threads:[~2017-04-03 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 7:30 Terrible bad performance for it blame --date=iso -C -C master -- <file> Ulrich Windl
2017-03-31 15:52 ` Junio C Hamano
2017-03-31 16:23 ` Samuel Lijin
2017-04-03 6:56 ` Antw: " Ulrich Windl
2017-04-03 10:56 ` Terrible bad performance for it blame --date=iso -C SZEDER Gábor
2017-04-03 15:16 ` Jakub Narębski [this message]
2017-04-04 6:23 ` Antw: " Ulrich Windl
2017-05-01 17:58 ` Terrible bad performance for it blame --date=iso -C -C master -- <file> Samuel Lijin
2017-05-02 0:59 ` Junio C Hamano
2017-05-03 7:12 ` Samuel Lijin
2017-05-03 12:29 ` Antw: " Ulrich Windl
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=0ccc5cab-26b7-4b02-b964-452b61e92579@gmail.com \
--to=jnareb@gmail.com \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).