From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v3 0/6] Nominating "whatchanged" for removal
Date: Fri, 2 May 2025 17:58:08 -0700 [thread overview]
Message-ID: <20250503005814.3030099-1-gitster@pobox.com> (raw)
In-Reply-To: <20250501225958.2947677-1-gitster@pobox.com>
"git whatchanged" has outlived its usefulness when "git log" with
various diff-related options more than 10 years ago. It is not even
shorter to type than its rough equivalent "git log --raw". It is
high time to start seeing if it is still being used, declare its
official deprecation, and announce its removal in the future.
This iteration is more complete than the previous two iterations:
* The first step is to refactor the mechanism to show the message
to ask users to contact git@vger that they still use the command,
out of "git pack-redundant" implementation. This message is
shown when the "--i-still-use-this" option is not passed to a
command that requires it.
* The second and the third step are to remove unnecessary mentions
of "whatchanged" from our documentation and tests. With these,
we have fewer places that we need to adjust when the command gets
truly removed.
* Then we start to require that the "--i-still-use-this" option is
passed from the command line. This requires adjustment for tests
that protect the behaviour of the command, as they must now pass
the required option just like end-users.
* The last two steps are for a future. In order to make sure that
we can cleanly ditch the feature at some future date by removing
it from the build, test, and documentation when Git is built with
WITH_BREAKING_CHANGES. And finally we add "whatchanged" to the
list of features to be removed in the BreakingChanges document.
Junio C Hamano (6):
you-still-use-that??: help deprecating commands for removal
doc: prepare for a world without whatchanged
tests: prepare for a world without whatchanged
whatchanged: require --i-still-use-this
whatchanged: remove when built with WITH_BREAKING_CHANGES
whatschanged: list it in BreakingChanges document
Documentation/BreakingChanges.adoc | 9 ++++++
Documentation/MyFirstObjectWalk.adoc | 4 +--
Documentation/config/format.adoc | 6 ++++
Documentation/config/log.adoc | 11 +++++--
Documentation/git-whatchanged.adoc | 10 ++++--
Documentation/pretty-options.adoc | 5 +++
Documentation/rev-list-options.adoc | 9 ++++--
Documentation/technical/sparse-checkout.adoc | 2 +-
Documentation/user-manual.adoc | 2 +-
builtin/log.c | 19 +++++++++++
builtin/pack-redundant.c | 10 ++----
git-compat-util.h | 2 ++
git.c | 2 ++
t/t4013-diff-various.sh | 27 ++++++++++++++--
t/t4202-log.sh | 34 ++++++++++++++------
t/t5323-pack-redundant.sh | 5 +++
t/t9300-fast-import.sh | 12 +++----
t/t9301-fast-import-notes.sh | 2 +-
usage.c | 12 +++++++
19 files changed, 146 insertions(+), 37 deletions(-)
--
2.49.0-601-ga5925c3955
next prev parent reply other threads:[~2025-05-03 0:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 21:34 [PATCH 0/2] Nominating "whatchanged" for removal Junio C Hamano
2025-05-01 21:34 ` [PATCH 1/2] you-still-use-that??: help deprecating commands " 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 ` Junio C Hamano [this message]
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=20250503005814.3030099-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).