From: Charles Diza <chdiza@gmail.com>
To: git@vger.kernel.org
Subject: v2.22.1 and later regression wrt display of progress indicators
Date: Thu, 22 Aug 2019 10:20:08 -0400 [thread overview]
Message-ID: <20190822141928.GA3163@323642-phi-gmno-clahs> (raw)
By 2.22.1 at the latest (and continuing into 2.23.0) there is a problem with the display of progress indication during `git pull` (and possibly other commands, I don't know).
I'm on macOS, and this happens in both Terminal.app and iTerm2.app, on both macOS 10.13.6 and 10.14.6: In a standard 80-column wide terminal window, cd into a git repo and do `git pull`. The chances are high (though not 100%) that one will see this:
remote: remote: Enumerating objects: 82, done.
remote: remote: remote: remote: remote:
[snip a large number of duplicate lines]
remote: remote:
remote: Counting objects: 100% (82/82), done.
remote: remote: remote: remote: remote: remote: remote: Compressing objects: 100% (5/5), done.
remote: Total 111 (delta 78), reused 78 (delta 77), pack-reused 29
It used to be that there were *no* lines that appear to consist just of "remote:". I say "appear" because most occurrences of "remote:" are followed by a bunch of spaces rather than linebreaks.
Charles
next reply other threads:[~2019-08-22 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 14:20 Charles Diza [this message]
2019-08-22 16:07 ` v2.22.1 and later regression wrt display of progress indicators SZEDER Gábor
2019-08-22 16:29 ` Jeff King
2019-08-22 16:40 ` SZEDER Gábor
2019-08-22 17:04 ` Jeff King
2019-08-22 17:19 ` Taylor Blau
2019-09-16 20:54 ` [PATCH 0/2] Revert "progress: use term_clear_line()" SZEDER Gábor
2019-09-16 20:54 ` [PATCH 1/2] " SZEDER Gábor
2019-09-16 20:54 ` [PATCH 2/2] Test the progress display SZEDER Gábor
2019-10-02 15:47 ` [PATCH 0/2] Revert "progress: use term_clear_line()" Jeff King
2019-08-22 17:16 ` v2.22.1 and later regression wrt display of progress indicators Taylor Blau
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=20190822141928.GA3163@323642-phi-gmno-clahs \
--to=chdiza@gmail.com \
--cc=git@vger.kernel.org \
/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).