diff options
| author | Justin Tobler <jltobler@gmail.com> | 2025-07-28 14:42:18 -0500 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2025-07-28 14:24:03 -0700 |
| commit | f609dc4f7a7cc8b57435696cac1cd0b056f9e8b9 (patch) | |
| tree | a392719fadc2a621edfdbb3a82fe742d732126b6 | |
| parent | 3f2a94875d2f41fe4758a439f68d8b73cfb19d0f (diff) | |
| download | git-f609dc4f7a7cc8b57435696cac1cd0b056f9e8b9.tar.gz | |
builtin: unmark git-switch and git-restore as experimental
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>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| -rw-r--r-- | Documentation/git-restore.adoc | 2 | ||||
| -rw-r--r-- | Documentation/git-switch.adoc | 2 |
2 files changed, 0 insertions, 4 deletions
diff --git a/Documentation/git-restore.adoc b/Documentation/git-restore.adoc index 877b7772e6..3763a7f4f4 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 9f62abf9e2..87707e9265 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>_:: |