git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/2] Nominating "whatchanged" for removal
Date: Thu,  1 May 2025 14:34:50 -0700	[thread overview]
Message-ID: <20250501213452.370729-1-gitster@pobox.com> (raw)

This does not go far enough to touch the "Git 3.0 removal" list in
Documentation/BreakingChanges.adoc, but is a preparatory step
necessary if we ever wanted to do so in the future.

The first step is to split out the long "we marked this for removal.
tell us at git@vger.kernel.org if you still use it, and in the
meantime we refuse to proceed without --i-still-use-this" message
out of "git pack-redundant" implementation and makes it reusable.

The second step is to use that helper to mark "git whatchanged" for
removal.

Junio C Hamano (2):
  you-still-use-that??: help deprecating commands for removal
  whatchanged: require --i-still-use-this

 Documentation/git-whatchanged.adoc | 10 ++++++++--
 builtin/log.c                      | 13 +++++++++++++
 builtin/pack-redundant.c           | 10 ++--------
 git-compat-util.h                  |  2 ++
 t/t4013-diff-various.sh            | 17 +++++++++++++++--
 t/t5323-pack-redundant.sh          |  5 +++++
 usage.c                            | 12 ++++++++++++
 7 files changed, 57 insertions(+), 12 deletions(-)

-- 
2.49.0-599-g90c2cffacf


             reply	other threads:[~2025-05-01 21:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01 21:34 Junio C Hamano [this message]
2025-05-01 21:34 ` [PATCH 1/2] you-still-use-that??: help deprecating commands for removal Junio C Hamano
2025-05-01 21:34 ` [PATCH 2/2] whatchanged: require --i-still-use-this Junio C Hamano
2025-05-01 22:23   ` Junio C Hamano
2025-05-01 22:59 ` [PATCH v2 0/2] Nominating "whatchanged" for removal Junio C Hamano
2025-05-01 22:59   ` [PATCH v2 1/2] you-still-use-that??: help deprecating commands " Junio C Hamano
2025-05-01 22:59   ` [PATCH v2 2/2] whatchanged: require --i-still-use-this Junio C Hamano
2025-05-02  9:08     ` Patrick Steinhardt
2025-05-02 16:49       ` Junio C Hamano
2025-05-05  6:10         ` Patrick Steinhardt
2025-05-02  9:08   ` [PATCH v2 0/2] Nominating "whatchanged" for removal Patrick Steinhardt
2025-05-02 16:46     ` Junio C Hamano
2025-05-03  0:58   ` [PATCH v3 0/6] " Junio C Hamano
2025-05-03  0:58     ` [PATCH v3 1/6] you-still-use-that??: help deprecating commands " Junio C Hamano
2025-05-12 17:35       ` Elijah Newren
2025-05-03  0:58     ` [PATCH v3 2/6] doc: prepare for a world without whatchanged Junio C Hamano
2025-05-12 17:36       ` Elijah Newren
2025-05-03  0:58     ` [PATCH v3 3/6] tests: " Junio C Hamano
2025-05-05  6:56       ` Patrick Steinhardt
2025-05-12 17:36       ` Elijah Newren
2025-05-03  0:58     ` [PATCH v3 4/6] whatchanged: require --i-still-use-this Junio C Hamano
2025-05-05  6:56       ` Patrick Steinhardt
2025-05-05 20:49         ` Junio C Hamano
2025-05-03  0:58     ` [PATCH v3 5/6] whatchanged: remove when built with WITH_BREAKING_CHANGES Junio C Hamano
2025-05-05  6:56       ` Patrick Steinhardt
2025-05-05 20:57         ` Junio C Hamano
2025-05-03  0:58     ` [PATCH v3 6/6] whatschanged: list it in BreakingChanges document Junio C Hamano
2025-05-12 17:36       ` Elijah Newren
2025-05-12 18:35         ` Junio C Hamano
2025-05-12 19:03     ` [PATCH v4 0/6] Nominating "whatchanged" for removal Junio C Hamano
2025-05-12 19:03       ` [PATCH v4 1/6] you-still-use-that??: help deprecating commands " Junio C Hamano
2025-05-12 19:03       ` [PATCH v4 2/6] doc: prepare for a world without whatchanged Junio C Hamano
2025-05-12 19:03       ` [PATCH v4 3/6] tests: " Junio C Hamano
2025-05-12 19:03       ` [PATCH v4 4/6] whatchanged: require --i-still-use-this Junio C Hamano
2025-05-14 13:38         ` Junio C Hamano
2025-05-12 19:03       ` [PATCH v4 5/6] whatchanged: remove when built with WITH_BREAKING_CHANGES Junio C Hamano
2025-05-12 19:03       ` [PATCH v4 6/6] whatschanged: list it in BreakingChanges document Junio C Hamano
2025-05-12 21:21       ` [PATCH v4 0/6] Nominating "whatchanged" for removal Elijah Newren
2025-05-12 22:42         ` Junio C Hamano

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=20250501213452.370729-1-gitster@pobox.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    /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).