Re: [PATCH v2] Documentation/git-worktree: fix stale "git checkout --to" references

[Junio C Hamano <gitster@pobox.com>]

Eric Sunshine <sunshine@sunshineco.com> writes:

> These should have been changed to "git worktree add" by fc56361
> (worktree: introduce "add" command, 2015-07-06.
>
> Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
> ---
>
> Changes since v1[1]: Reference the correct commit (fc56361, not b979d95)
> in the commit message. Sorry for the noise.
>
> [1]: http://article.gmane.org/gmane.comp.version-control.git/274046

Thanks.  Will apply.

By the way, given the rate of bugs and glitches I am finding in this
code with a very superficial use in real work only for a few days,
perhaps we would want to add a warning to the documentation of "git
worktree", in addition to the "this is still experimental" mention
in the release notes, to discourage people to keep their only copy
of the work in a secondary worktree for now?



 Documentation/git-worktree.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt
index da71f50..6de4c21 100644
--- a/Documentation/git-worktree.txt
+++ b/Documentation/git-worktree.txt
@@ -157,8 +157,9 @@ $ git worktree prune
 
 BUGS
 ----
-Multiple checkout support for submodules is incomplete. It is NOT
-recommended to make multiple checkouts of a superproject.
+Multiple checkout in general is still experimental, and the support
+for submodules is incomplete. It is NOT recommended to make multiple
+checkouts of a superproject.
 
 git-worktree could provide more automation for tasks currently
 performed manually, such as: