Declare both git-switch and git-restore experimental
authorNguyễn Thái Ngọc Duy <pclouds@gmail.com>
Thu, 25 Apr 2019 09:46:00 +0000 (16:46 +0700)
committerJunio C Hamano <gitster@pobox.com>
Tue, 7 May 2019 04:04:48 +0000 (13:04 +0900)
These two commands are basically redesigned git-checkout. We will not
have that many opportunities to redo (because we run out of verbs, and
that would also increase maintenance cost).

To play it safe, let's declare the two commands experimental in one or
two releases. If there is a serious flaw in the UI, we could still fix
it. If everything goes well and nobody complains loudly, we can remove
the experimental status by reverting this patch.

Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-restore.txt
Documentation/git-switch.txt
index b608f3f3606b416dd4a374fca4de801cabbab1d2..d90093f195bc6a9b2b3d2d20be89c59e4d708739 100644 (file)
@@ -28,6 +28,8 @@ commit as the restore source.
 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>::
index f15e5bdcf414f9c81a291ebc70d45dd59e377d9f..197900363b0b7daa273fc2b39f7bed6961f08e09 100644 (file)
@@ -29,6 +29,8 @@ 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>::