git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org,  Jeff King <peff@peff.net>,
	 Taylor Blau <me@ttaylorr.com>
Subject: Re: [PATCH] Documentation/BreakingChanges: announce removal of git-pack-redundant(1)
Date: Tue, 03 Sep 2024 11:31:31 -0700	[thread overview]
Message-ID: <xmqqy148k2rg.fsf@gitster.g> (raw)
In-Reply-To: <a6be9f5e9eb1f426b1a17b89e3db1bc7532758b5.1725264748.git.ps@pks.im> (Patrick Steinhardt's message of "Mon, 2 Sep 2024 10:13:00 +0200")

Patrick Steinhardt <ps@pks.im> writes:

> The git-pack-redundant(1) command is already in the process of being
> phased out and dies unless the user passes the `--i-still-use-this` flag
> since 4406522b76 (pack-redundant: escalate deprecation warning to an
> error, 2023-03-23). We haven't heard any complaints, so let's announce
> the removal of this command in Git 3.0 in our breaking changes document.
>
> Signed-off-by: Patrick Steinhardt <ps@pks.im>
> ---
>  Documentation/BreakingChanges.txt | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)


Finally ;-)

The "--i-still-use-this" (unless major distros have stripped it out)
was a good approach to allow us do this.

Will queue.  Thanks.


> diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt
> index 0532bfcf7f9..2b64665694f 100644
> --- a/Documentation/BreakingChanges.txt
> +++ b/Documentation/BreakingChanges.txt
> @@ -115,6 +115,26 @@ info/grafts as outdated, 2014-03-05) and will be removed.
>  +
>  Cf. <20140304174806.GA11561@sigill.intra.peff.net>.
>  
> +* The git-pack-redundant(1) command can be used to remove redundant pack files.
> +  The subcommand is unusably slow and the reason why nobody reports it as a
> +  performance bug is suspected to be the absense of users. We have nominated
> +  the command for removal and have started to emit a user-visible warning in
> +  c3b58472be (pack-redundant: gauge the usage before proposing its removal,
> +  2020-08-25) whenever the command is executed.
> ++
> +So far there was a single complaint about somebody still using the command, but
> +that complaint did not cause us to reverse course. On the contrary, we have
> +doubled down on the deprecation and starting with 4406522b76 (pack-redundant:
> +escalate deprecation warning to an error, 2023-03-23), the command dies unless
> +the user passes the `--i-still-use-this` option.
> ++
> +There have not been any subsequent complaints, so this command will finally be
> +removed.
> ++
> +Cf. <xmqq1rjuz6n3.fsf_-_@gitster.c.googlers.com>,
> +    <CAKvOHKAFXQwt4D8yUCCkf_TQL79mYaJ=KAKhtpDNTvHJFuX1NA@mail.gmail.com>,
> +    <20230323204047.GA9290@coredump.intra.peff.net>,
> +
>  == Superseded features that will not be deprecated
>  
>  Some features have gained newer replacements that aim to improve the design in

      reply	other threads:[~2024-09-03 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  8:13 [PATCH] Documentation/BreakingChanges: announce removal of git-pack-redundant(1) Patrick Steinhardt
2024-09-03 18:31 ` Junio C Hamano [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=xmqqy148k2rg.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=peff@peff.net \
    --cc=ps@pks.im \
    /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).