Re: [PATCH 19/19] doc: promote "git switch"
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Jan 31, 2019, 11:28 UTC
- Message-ID
- <CACsJy8DEeK7wbDJbk_mVkRjU2rFz7EvRyYRwf8N_8pt+sDKX3w@mail.gmail.com>
- In-Reply-To
- <CAPig+cRJJtZv0LcchXhV5FFOnbJTVio9Y_R8hyvGJEAGLsJ69A@mail.gmail.com>
On Thu, Jan 31, 2019 at 2:39 PM Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 10 quoted lines
> > diff --git a/builtin/clone.c b/builtin/clone.c
> > @@ -491,7 +491,7 @@ static enum {
> > static const char junk_leave_repo_msg[] =
> > N_("Clone succeeded, but checkout failed.\n"
> > "You can inspect what was checked out with 'git status'\n"
> > - "and retry the checkout with 'git checkout -f HEAD'\n");
> > + "and retry the checkout with 'git switch -f HEAD'\n");
>
> Just wondering if these uses of "checkout" and "checked out" need
> adjustment. I don't have any good suggestions, though.I think I'm going to leave this message alone for now. Technically "git switch" can replace "git checkout" here but I feel this is more about restoring files on worktree than switching branches. So when "git restore" comes, I'll change it to say "git restore --from=HEAD :/" or something like that instead.
-- Duy