git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 (Dec 2021, #05; Thu, 23))
Date: Sun, 26 Dec 2021 18:24:11 +0100	[thread overview]
Message-ID: <211226.86y247ff9b.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqsfui6g7q.fsf@gitster.g>


On Thu, Dec 23 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>

This is the v6, but I submitted a v7 on December 17th that should
address the outstanding questions about this series, i.e. it ejected the
controversial last patch adding the BUG(). I can pursue that later,
which should make its review easier.

I inadvertently broke threading in the v7 submission, sorry about that,
but here it is:
https://lore.kernel.org/git/cover-v7-0.7-00000000000-20211217T041945Z-avarab@gmail.com/

And the old v6 you've got here is at:
https://lore.kernel.org/git/cover-v6-0.8-00000000000-20211102T122507Z-avarab@gmail.com/

      parent reply	other threads:[~2021-12-26 17:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 23:42 What's cooking in git.git (Dec 2021, #05; Thu, 23) Junio C Hamano
2021-12-24 17:29 ` ab/make-dependency (was "What's cooking in git.git (Dec 2021, #05; Thu, 23)) Ævar Arnfjörð Bjarmason
2021-12-26 18:51   ` Junio C Hamano
2021-12-25  1:55 ` What's cooking in git.git (Dec 2021, #05; Thu, 23) Junio C Hamano
2021-12-25  2:49   ` ds/sparse-checkout-requires-per-worktree-config (Was: Re: What's cooking in git.git (Dec 2021, #05; Thu, 23)) Elijah Newren
2021-12-25 22:20     ` ds/sparse-checkout-requires-per-worktree-config Junio C Hamano
2021-12-25  6:44   ` What's cooking in git.git (Dec 2021, #05; Thu, 23) Eric Sunshine
2021-12-25 12:07 ` Teng Long
2021-12-26 17:15   ` Ævar Arnfjörð Bjarmason
2021-12-27  7:09     ` Teng Long
2021-12-26 17:24 ` Ævar Arnfjörð Bjarmason [this message]

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=211226.86y247ff9b.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.
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).