All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3 5/6] whatchanged: remove when built with WITH_BREAKING_CHANGES
Date: Mon, 05 May 2025 13:57:53 -0700	[thread overview]
Message-ID: <xmqqbjs6ojvy.fsf@gitster.g> (raw)
In-Reply-To: <aBhhDAZTLJQTIQSC@pks.im> (Patrick Steinhardt's message of "Mon, 5 May 2025 08:56:12 +0200")

Patrick Steinhardt <ps@pks.im> writes:

> On Fri, May 02, 2025 at 05:58:13PM -0700, Junio C Hamano wrote:
>> As we made "git whatchanged" require "--i-still-use-this" and asked
>> the users to report if they still want to use it, the logical next
>> step is to allow us build Git without "whatchanged" to prepare for
>> its eventual removal.
>> 
>> If we were to follow the pattern established in 8ccc75c2 (remote:
>> announce removal of "branches/" and "remotes/", 2025-01-22), we can
>> do this together with the documentation update to officially list
>> that the command will be removed in the BreakingChanges document,
>> but let's just keep the changes separate just in case we want to
>> proceed a bit slower.
>
> We'd also need to adjust Meson so that it doesn't install the
> documentation anymore. So something like the below (untested) patch.

Thanks.

> diff --git a/Documentation/Makefile b/Documentation/Makefile
> index b109d25e9c8..815b0334e53 100644
> --- a/Documentation/Makefile
> +++ b/Documentation/Makefile
> @@ -510,7 +510,7 @@ lint-docs-meson:
>  	awk "/^manpages = {$$/ {flag=1 ; next } /^}$$/ { flag=0 } flag { gsub(/^  \047/, \"\"); gsub(/\047 : [157],\$$/, \"\"); print }" meson.build | \
>  		grep -v -e '#' -e '^$$' | \
>  		sort >tmp-meson-diff/meson.adoc && \
> -	ls git*.adoc scalar.adoc | grep -v -e git-bisect-lk2009.adoc -e git-pack-redundant.adoc -e git-tools.adoc >tmp-meson-diff/actual.adoc && \
> +	ls git*.adoc scalar.adoc | grep -v -e git-bisect-lk2009.adoc -e git-pack-redundant.adoc -e git-whatchanged.adoc -e git-tools.adoc >tmp-meson-diff/actual.adoc && \

Yuck.

> diff --git a/Documentation/meson.build b/Documentation/meson.build
> index 1433acfd310..2fe1a1369d4 100644
> --- a/Documentation/meson.build
> +++ b/Documentation/meson.build
> @@ -158,7 +158,6 @@ manpages = {
>    'git-verify-tag.adoc' : 1,
>    'git-version.adoc' : 1,
>    'git-web--browse.adoc' : 1,
> -  'git-whatchanged.adoc' : 1,
>    'git-worktree.adoc' : 1,
>    'git-write-tree.adoc' : 1,
>    'git.adoc' : 1,
> @@ -207,6 +206,7 @@ manpages = {
>  
>  manpages_breaking_changes = {
>    'git-pack-redundant.adoc' : 1,
> +  'git-whatchanged.adoc' : 1,
>  }

OK.

Thanks.

  reply	other threads:[~2025-05-05 20:57 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   ` [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 [this message]
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=xmqqbjs6ojvy.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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 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.