From: Junio C Hamano <gitster@pobox.com>
To: Justin Tobler <jltobler@gmail.com>
Cc: git@vger.kernel.org, ps@pks.im
Subject: Re: [PATCH 0/2] builtin: unmark git-switch and git-restore as experimental
Date: Tue, 22 Jul 2025 13:22:11 -0700 [thread overview]
Message-ID: <xmqqldogrn64.fsf@gitster.g> (raw)
In-Reply-To: <20250722180818.1043014-1-jltobler@gmail.com> (Justin Tobler's message of "Tue, 22 Jul 2025 13:08:16 -0500")
Justin Tobler <jltobler@gmail.com> writes:
> Greetings,
>
> In 4e43b7ff (Declare both git-switch and git-restore experimental,
> 2019-04-25), the newly introduced git-switch(1) and git-restore(1)
> commands were marked as experimental. This was done to provide time to
> make breaking changes to the interface. It has now been over six years
> since these commands were implemented and, over this time, there has not
> been much change that would warrant these commands being labeled as
> experimental.
Do you mean "as not experimental anymore", don't you? We were
hoping that we would come up with vast UI improvements, that are so
much better that warrant departure from the past, allowing us room
to even break the backward compatibility. Unfortunately, we do not
have much to show after 5 years. But ...
> At this point, it seems rather difficult to justify changing
> `-c/--create` to something different as it has been that way for a long
> time and is used frequently.
... yeah, people grew to rely on that experimental UI that we added,
with intention to revamp and replace with much better alternative,
and now it is too late to change it.
> By removing the experimental marker, we help clarify the stability and
> maturity of these commands.
So, even though I may agree with the conclusion that we no longer
would allow ourselves to break backward compatibility for these two
commands, I doubt that it is stability and maturity to celebrate
about. It (not the "have two speparate commands" part, but "leave
ourselves room to improve these two commands" part) was a clearly
failed experiment.
next prev parent reply other threads:[~2025-07-22 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 18:08 [PATCH 0/2] builtin: unmark git-switch and git-restore as experimental Justin Tobler
2025-07-22 18:08 ` [PATCH 1/2] builtin: remove merge short flag for switch and restore Justin Tobler
2025-07-22 20:54 ` Junio C Hamano
2025-07-22 21:16 ` Justin Tobler
2025-07-22 18:08 ` [PATCH 2/2] builtin: unmark git-switch and git-restore as experimental Justin Tobler
2025-07-22 21:00 ` Junio C Hamano
2025-07-22 21:20 ` Justin Tobler
2025-07-22 20:22 ` Junio C Hamano [this message]
2025-07-22 21:32 ` [PATCH 0/2] " Justin Tobler
2025-07-28 19:42 ` [PATCH] " Justin Tobler
2025-07-28 20:52 ` 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=xmqqldogrn64.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
--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 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).