From: "Ævar Arnfjörð Bjarmason" <email@example.com> To: Felipe Contreras <firstname.lastname@example.org> Cc: "Junio C Hamano" <email@example.com>, "Elijah Newren" <firstname.lastname@example.org>, "Gábor Farkas" <email@example.com>, "Git Mailing List" <firstname.lastname@example.org> Subject: Re: git switch/restore, still experimental? Date: Thu, 06 May 2021 17:26:37 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Thu, May 06 2021, Felipe Contreras wrote: > Junio C Hamano wrote: >> Ævar Arnfjörð Bjarmason <email@example.com> writes: >> >> > I mean, I see why. You don't want a typo of "master" as "maaster" to >> > create a new "maaster" branch, so really that's out. But it really >> > should be: >> > >> > # -n or -N for --new / --new --force (the latter just in case of a >> > # race, and just for consistency) >> > git switch -n doesnotexist >> >> I do not see why --new is better than --create; > > I do. Different languages equal different minds. > > New in this context is an adjetive: it is a modifier of a noun, in this > case, a branch. > > Create is a verb; it's an action. > > Linguistically speaking they could not be more different. > > > You don't do two verbs at a time. Either you sleep, or you eat, but you > don't do both. Similarly you don't switch and create. Doesn't make > sense. > > If you use natural language: > > 1. Git, switch to a new branch > > 2. Git, switch, create, branch > > One of these simply flows, the other is complete gibberish. I think > anyone familiar with English can identify which is which. Well, there's "Git, create a new branch and switch to it" Also, there's the verb "make" in common use in git's command set e.g. git-mktag, git-mktree, as well as mkdir(1), mkfifo(1) etc. Perhaps we'd be better off with a git-mkbranch in this case & leave "git branch" as an interrogation/change command. In any case, unless we're talking about rewamping git's entire command set (e.g. having a git-newtree or whatever) I'd like to think that it's more productive to focus on making the commands/switches we have internally consistent when possible, which is what I'm advocating in the E-Mail that started this sub-thread.
next prev parent reply other threads:[~2021-05-06 15:30 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-04 10:32 Gábor Farkas 2021-05-04 19:54 ` Felipe Contreras 2021-05-05 3:46 ` Elijah Newren 2021-05-05 4:01 ` Eric Sunshine 2021-05-05 11:09 ` Ævar Arnfjörð Bjarmason 2021-05-05 17:46 ` Felipe Contreras 2021-05-05 19:26 ` Sergey Organov 2021-05-05 19:48 ` Sergey Organov 2021-05-06 1:39 ` Junio C Hamano 2021-05-06 15:19 ` Sergey Organov 2021-05-06 10:05 ` Ævar Arnfjörð Bjarmason 2021-05-06 14:29 ` Sergey Organov 2021-05-06 2:16 ` Junio C Hamano 2021-05-06 10:02 ` Ævar Arnfjörð Bjarmason 2021-05-10 11:04 ` Ævar Arnfjörð Bjarmason 2021-05-10 18:27 ` Junio C Hamano 2021-05-06 11:00 ` Felipe Contreras 2021-05-06 15:26 ` Ævar Arnfjörð Bjarmason [this message] 2021-05-06 21:55 ` Felipe Contreras 2021-05-10 10:58 ` Ævar Arnfjörð Bjarmason 2021-05-11 7:15 ` Felipe Contreras 2021-05-05 14:18 ` Johannes Schindelin 2021-05-05 14:26 ` Randall S. Becker 2021-05-06 1:15 ` Junio C Hamano 2021-05-05 17:52 ` Felipe Contreras
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: git switch/restore, still experimental?' \ /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
Code repositories for project(s) associated with this 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).