From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes Altmanninger <aclopte@gmail.com>
Subject: ab/only-single-progress-at-once (was: What's cooking in git.git (Dec 2021, #06; Mon, 27))
Date: Tue, 28 Dec 2021 16:20:29 +0100 [thread overview]
Message-ID: <211228.86czlgiwkp.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqq7dbpvb0q.fsf@gitster.g>
On Mon, Dec 27 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.
>
> Needs review.
> The last three rounds has seen little reaction, even though earlier
> round saw a lot of responses. The latest round needs a serious
> review or at least Acks from past commentors.
> source: <cover-v6-0.8-00000000000-20211102T122507Z-avarab@gmail.com>
The slimmed-down v7 got a review from Johannes Altmanninger, and I've
just submitted a v8 now to address the points brought up there:
https://lore.kernel.org/git/cover-v8-0.7-00000000000-20211228T150728Z-avarab@gmail.com/
next prev parent reply other threads:[~2021-12-28 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 0:16 What's cooking in git.git (Dec 2021, #06; Mon, 27) Junio C Hamano
2021-12-28 13:31 ` ab/cat-file (was: What's cooking in git.git (Dec 2021, #06; Mon, 27)) Ævar Arnfjörð Bjarmason
2021-12-28 13:40 ` hn/reftable-coverity-fixes " Ævar Arnfjörð Bjarmason
2021-12-28 14:35 ` ab/ambiguous-object-name " Ævar Arnfjörð Bjarmason
2021-12-28 15:20 ` Ævar Arnfjörð Bjarmason [this message]
2021-12-28 17:42 ` What's cooking in git.git (Dec 2021, #06; Mon, 27) Elijah Newren
2021-12-30 23:56 ` Junio C Hamano
2022-01-04 22:20 ` Glen Choo
2022-01-10 18:41 ` Junio C Hamano
2022-01-01 14:01 ` tl/ls-tree-oid-only (was: What's cooking in git.git (Dec 2021, #06; Mon, 27)) Teng Long
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=211228.86czlgiwkp.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=aclopte@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.
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 NNTP newsgroup(s).