From: <rsbecker@nexbridge.com>
To: "'Eric Sunshine'" <sunshine@sunshineco.com>
Cc: "'Junio C Hamano'" <gitster@pobox.com>,
"'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, 9 Jan 2023 14:58:14 -0500 [thread overview]
Message-ID: <01ad01d92464$b62492c0$226db840$@nexbridge.com> (raw)
In-Reply-To: <CAPig+cQ1PMYhWiwRiq2eOWzHYmqcCC6QfkHCuVTxaeA7fz0ddw@mail.gmail.com>
On January 9, 2023 2:17 PM, Eric Sunshine wrote:
>On Mon, Jan 9, 2023 at 6:20 AM <rsbecker@nexbridge.com> wrote:
>> On January 8, 2023 11:31 PM, Junio C Hamano wrote:
>> >"Yutaro Ohno via GitGitGadget" <gitgitgadget@gmail.com> writes:
>> >> Subject: Re: [PATCH] doc: use "git switch -c" rather than "git
>> >> checkout -b" consistently
>> >
>> >Hmph. When two things work equally well, is it a good idea to
>> >describe
>> only one
>> >"consistently", or mention both that can be used pretty much
>> interchangeably in
>> >different places? I am not 100% sure "consistently" is a good thing here.
>> >
>> >Thoughts from others?
>>
>> git switch is still marked as EXPERIMENTAL in the online help. I don't
>> think moving broadly to switch from checkout in the documentation
>> should happen until the EXPERIMENTAL designation is dropped. After that, then
>"switch -c"
>> should be used everywhere instead of checkout (except for in the
>> checkout documentation).
>
>Such a point probably should have been raised when 328c6cb853 (doc:
>promote "git switch", 2019-03-29) was submitted, but since 328c6cb853 was
>merged nearly four years ago and has been pointing people at git-switch all this
>time, it's probably too late to use it as an argument now.
I agree. Perhaps it is time to drop the "EXPERIMENTAL" notices from 'git switch', in that case.
next prev parent reply other threads:[~2023-01-09 19:59 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
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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01ad01d92464$b62492c0$226db840$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).