From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Yutaro Ohno via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Yutaro Ohno <yutaro.ono.418@gmail.com>
Subject: Re: [PATCH] doc: use "git switch -c" rather than "git checkout -b" consistently
Date: Mon, 09 Jan 2023 15:30:28 +0900 [thread overview]
Message-ID: <xmqqk01wusmz.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cQe_VMW2KV+ZyZwosFw07Q+hePryDVushRJ-jFfD4yzpw@mail.gmail.com> (Eric Sunshine's message of "Sun, 8 Jan 2023 23:48:46 -0500")
Eric Sunshine <sunshine@sunshineco.com> writes:
> touches is given merely as examples one might use, then I could see
> git-switch being prepended to the list rather than entirely replacing
> git-checkout. For instance:
>
> If we have not yet moved away from commit `f`,
> any of these will create a reference to it:
>
> ------------
> $ git switch -c foo <1>
> $ git checkout -b foo <1>
> $ git branch foo <2>
> $ git tag foo <3>
> ------------
That can invite "do we need to use checkout after doing switch?"
confusion. I would understand if it were
$ git checkout -b foo # or "git switch -c foo" <1>
or something that makes it clear either one, but not both, is used
there.
Thanks.
next prev parent reply other threads:[~2023-01-09 6:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 8:24 [PATCH] doc: use "git switch -c" rather than "git checkout -b" consistently Yutaro Ohno via GitGitGadget
2023-01-09 4:30 ` Junio C Hamano
2023-01-09 4:48 ` Eric Sunshine
2023-01-09 6:30 ` Junio C Hamano [this message]
2023-01-09 6:32 ` Eric Sunshine
2023-01-09 8:47 ` Yutaro Ohno
2023-01-09 11:17 ` rsbecker
2023-01-09 19:16 ` Eric Sunshine
2023-01-09 19:58 ` rsbecker
2023-01-09 21:08 ` Eric Sunshine
2023-01-09 21:24 ` Ævar Arnfjörð Bjarmason
2023-01-09 10:47 ` [PATCH v2] doc: add "git switch -c" as another option on detached HEAD Yutaro Ohno via GitGitGadget
2023-01-09 19:53 ` Eric Sunshine
2023-01-13 17:58 ` Junio C Hamano
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=xmqqk01wusmz.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=sunshine@sunshineco.com \
--cc=yutaro.ono.418@gmail.com \
/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.