From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v2 0/6] drop "name-rev --stdin" support
Date: Tue, 11 Mar 2025 14:24:59 -0700 [thread overview]
Message-ID: <20250311212505.2920181-1-gitster@pobox.com> (raw)
In-Reply-To: <20250310231652.3742490-1-gitster@pobox.com>
During Git 2.40 timeframe, we deprecated the "--stdin" option of the
"name-rev" command in preference to the "--annotate-stdin" option,
and removed the mention of the former from the documentation.
Let's prepare for Git 3.0 to stop supporting it.
The real motive of these patches is not really about that particular
option but make sure we have, with WITH_BREAKING_CHANGES compilation
knob, enough support to keep preparing for these changes.
The first two patches are preliminary clean-up and enhancement.
We lacked documentation on test_lazy_prereq and we did not have a
good way to signal a prerequisite that no longer should be used,
both of which are remedied.
The third patch renames the WITHOUT_BREAKING_CHANGES prerequisite
that unfortunately invites double negations easily and changes
existing users of it.
Then two patches to a test script minimally modernizes it.
The last step introduces the real change, guarded by
WITH_BREAKING_CHANGES compilation knob. The resulting code is more
littered with #if[n]def compared to the previous round but it should
be clear which section of the code should go away once we do Git
3.0, which is the whole point of the WITH_BREAKING_CHANGES exercise.
Junio C Hamano (6):
t: document test_lazy_prereq
t: extend test_lazy_prereq
t: introduce WITH_BREAKING_CHANGES prerequisite
t6120: avoid hiding "git" exit status
t6120: further modernize
name-rev: remove "--stdin" support
Documentation/BreakingChanges.adoc | 6 ++++++
builtin/name-rev.c | 10 +++++++++-
t/README | 25 ++++++++++++++++++++++++-
t/t5323-pack-redundant.sh | 2 +-
t/t5505-remote.sh | 6 +++---
t/t5515-fetch-merge-logic.sh | 2 +-
t/t5516-fetch-push.sh | 8 ++++----
t/t6120-describe.sh | 18 +++++++++++++-----
t/test-lib-functions.sh | 5 +++++
t/test-lib.sh | 7 ++++++-
10 files changed, 72 insertions(+), 17 deletions(-)
--
2.49.0-rc2-181-g28e223d67e
next prev parent reply other threads:[~2025-03-11 21:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 23:16 [PATCH v1 0/4] drop "name-rev --stdin" support Junio C Hamano
2025-03-10 23:16 ` [PATCH v1 1/4] t: introduce WITH_BREAKING_CHANGES prerequisite Junio C Hamano
2025-03-10 23:53 ` Eric Sunshine
2025-03-11 12:57 ` Patrick Steinhardt
2025-03-11 17:07 ` Junio C Hamano
2025-03-10 23:16 ` [PATCH v1 2/4] t6120: avoid hiding "git" exit status Junio C Hamano
2025-03-10 23:16 ` [PATCH v1 3/4] t6120: further modernize Junio C Hamano
2025-03-10 23:16 ` [PATCH v1 4/4] name-rev: remove "--stdin" support Junio C Hamano
2025-03-11 12:57 ` Patrick Steinhardt
2025-03-11 17:07 ` Junio C Hamano
2025-03-11 21:24 ` Junio C Hamano [this message]
2025-03-11 21:25 ` [PATCH v2 1/6] t: document test_lazy_prereq Junio C Hamano
2025-03-11 21:25 ` [PATCH v2 2/6] t: extend test_lazy_prereq Junio C Hamano
2025-03-12 7:01 ` Patrick Steinhardt
2025-03-13 11:56 ` Junio C Hamano
2025-03-11 21:25 ` [PATCH v2 3/6] t: introduce WITH_BREAKING_CHANGES prerequisite Junio C Hamano
2025-03-12 7:01 ` Patrick Steinhardt
2025-03-11 21:25 ` [PATCH v2 4/6] t6120: avoid hiding "git" exit status Junio C Hamano
2025-03-11 21:25 ` [PATCH v2 5/6] t6120: further modernize Junio C Hamano
2025-03-11 21:25 ` [PATCH v2 6/6] name-rev: remove "--stdin" support 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=20250311212505.2920181-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).