From: Junio C Hamano <gitster@pobox.com>
To: Justin Tobler <jltobler@gmail.com>
Cc: git@vger.kernel.org, ps@pks.im
Subject: Re: [PATCH] builtin: unmark git-switch and git-restore as experimental
Date: Mon, 28 Jul 2025 13:52:01 -0700 [thread overview]
Message-ID: <xmqq1pq0ujgu.fsf@gitster.g> (raw)
In-Reply-To: <20250728194218.2379432-1-jltobler@gmail.com> (Justin Tobler's message of "Mon, 28 Jul 2025 14:42:18 -0500")
Justin Tobler <jltobler@gmail.com> writes:
> 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 there hasn't been much change.
> Consequently, users have grown to rely on how these commands work and it
> is no longer feasible to make any breaking changes.
>
> Let's remove the experimental label for git-switch(1) and
> git-restore(1).
>
> Signed-off-by: Justin Tobler <jltobler@gmail.com>
> ---
> Documentation/git-restore.adoc | 2 --
> Documentation/git-switch.adoc | 2 --
> 2 files changed, 4 deletions(-)
Thanks for tying loose ends. This completely slipped my mind.
Will queue. Thanks.
> diff --git a/Documentation/git-restore.adoc b/Documentation/git-restore.adoc
> index 877b7772e66..3763a7f4f43 100644
> --- a/Documentation/git-restore.adoc
> +++ b/Documentation/git-restore.adoc
> @@ -28,8 +28,6 @@ otherwise from the index. Use `--source` to restore from a different commit.
> See "Reset, restore and revert" in linkgit:git[1] for the differences
> between the three commands.
>
> -THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.
> -
> OPTIONS
> -------
> `-s <tree>`::
> diff --git a/Documentation/git-switch.adoc b/Documentation/git-switch.adoc
> index 9f62abf9e2b..87707e92652 100644
> --- a/Documentation/git-switch.adoc
> +++ b/Documentation/git-switch.adoc
> @@ -29,8 +29,6 @@ Switching branches does not require a clean index and working tree
> however if the operation leads to loss of local changes, unless told
> otherwise with `--discard-changes` or `--merge`.
>
> -THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.
> -
> OPTIONS
> -------
> _<branch>_::
prev parent reply other threads:[~2025-07-28 20:52 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 ` [PATCH 0/2] " Junio C Hamano
2025-07-22 21:32 ` Justin Tobler
2025-07-28 19:42 ` [PATCH] " Justin Tobler
2025-07-28 20:52 ` Junio C Hamano [this message]
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=xmqq1pq0ujgu.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 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.