From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v1 0/4] drop "name-rev --stdin" support
Date: Mon, 10 Mar 2025 16:16:48 -0700 [thread overview]
Message-ID: <20250310231652.3742490-1-gitster@pobox.com> (raw)
[Administrivia]
Yes, yes, I know I shouldn't be playing with shiny new toys
during the pre-release freeze time. But just to show others who
may still be doing so that the first patch in this series has
already be written to avoid duplicated and conflicting work, I
am sending them out. I have no intention to push the topic
further before the final.
During Git 2.40 timeframe, we deprecated "--stdin" option of the
"name-rev" command in preference to "--annotate-stdin", and removed
the mention of it 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 option but
make sure we have, with WITH_BREAKING_CHANGES compilation knob,
enough support to keep preparing these changes. The first 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.
Junio C Hamano (4):
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 | 2 ++
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.sh | 5 +++++
8 files changed, 35 insertions(+), 14 deletions(-)
--
2.49.0-rc2-173-g4d16673c2b
next reply other threads:[~2025-03-10 23:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 23:16 Junio C Hamano [this message]
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 ` [PATCH v2 0/6] drop "name-rev --stdin" support Junio C Hamano
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=20250310231652.3742490-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 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.