From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/only-single-progress-at-once (was: What's cooking in git.git (Nov 2021, #04; Sun, 14))
Date: Mon, 15 Nov 2021 20:35:25 +0100 [thread overview]
Message-ID: <211115.86wnl9qkfz.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqv90tfhh2.fsf@gitster.g>
On Mon, Nov 15 2021, Junio C Hamano wrote:
> * ab/only-single-progress-at-once (2021-11-03) 8 commits
> - progress.c: add & assert a "global_progress" variable
> - various *.c: use isatty(0|2), not isatty(STDIN_FILENO|STDERR_FILENO)
> - pack-bitmap-write.c: don't return without stop_progress()
> - progress.c: add temporary variable from progress struct
> - progress.c tests: test some invalid usage
> - progress.c tests: make start/stop commands on stdin
> - progress.c test helper: add missing braces
> - leak tests: fix a memory leaks in "test-progress" helper
>
> Further tweaks on progress API.
It would be great to get this one marked for "next". I think all
outstanding feedback was addressed ([1] for the last CL), and for a
topic that's adding we haven't had any reports of the BUG() assertion it
adds firing (and I've done some very thorough testing to make sure it
won't, per the 8/8 commit message[2]).
1. https://lore.kernel.org/git/cover-v6-0.8-00000000000-20211102T122507Z-avarab@gmail.com/
2. https://lore.kernel.org/git/patch-v6-8.8-bff919994b5-20211102T122507Z-avarab@gmail.com/
next prev parent reply other threads:[~2021-11-15 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 17:37 What's cooking in git.git (Nov 2021, #04; Sun, 14) Junio C Hamano
2021-11-15 19:30 ` ab/mark-leak-free-tests-even-more (was: What's cooking in git.git (Nov 2021, #04; Sun, 14)) Ævar Arnfjörð Bjarmason
2021-11-15 22:16 ` Elijah Newren
2021-11-15 19:35 ` Ævar Arnfjörð Bjarmason [this message]
2021-11-15 19:37 ` ab/refs-errno-cleanup + hn/reftable " Ævar Arnfjörð Bjarmason
2021-11-15 20:00 ` What's cooking in git.git (Nov 2021, #04; Sun, 14) Fabian Stelzer
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=211115.86wnl9qkfz.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).