From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, peff@peff.net, szeder.dev@gmail.com,
avarab@gmail.com, dstolee@microsoft.com
Subject: Re: [PATCH 0/1] commit-graph: drop top-level --[no-]progress
Date: Mon, 20 Sep 2021 14:24:04 -0700 [thread overview]
Message-ID: <xmqqr1dj9c0b.fsf@gitster.g> (raw)
In-Reply-To: <cover.1631980949.git.me@ttaylorr.com> (Taylor Blau's message of "Sat, 18 Sep 2021 12:02:34 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> An open question is whether the same should be done for the multi-pack-index
> command, whose top-level support for `--[no-]progress` was released in v2.32.0
> with 60ca94769c (builtin/multi-pack-index.c: split sub-commands, 2021-03-30).
We do not mind too much about "breaking backward compatibility" by
removing the mistaken "git multi-pack-index --progress cmd", I would
say. It's not like people would type it once every day and removing
the "support" will break their finger-memory.
next prev parent reply other threads:[~2021-09-20 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 16:02 [PATCH 0/1] commit-graph: drop top-level --[no-]progress Taylor Blau
2021-09-18 16:02 ` [PATCH 1/1] builtin/commit-graph.c: don't accept common --[no-]progress Taylor Blau
2021-09-20 12:46 ` Derrick Stolee
2021-09-20 15:02 ` Taylor Blau
2021-09-20 21:24 ` Junio C Hamano [this message]
2021-09-20 21:39 ` [PATCH 0/1] commit-graph: drop top-level --[no-]progress Taylor Blau
2021-09-21 18:19 ` Ævar Arnfjörð Bjarmason
2021-09-21 20:38 ` Taylor Blau
2021-09-22 16:22 ` Junio C Hamano
2021-09-21 3:55 ` Jeff King
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=xmqqr1dj9c0b.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.