From: Junio C Hamano <email@example.com> To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org> Cc: "Elijah Newren" <email@example.com>, "Gábor Farkas" <firstname.lastname@example.org>, "Git Mailing List" <email@example.com> Subject: Re: git switch/restore, still experimental? Date: Tue, 11 May 2021 03:27:56 +0900 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (=?utf-8?B?IsOGdmFyIEFy?= =?utf-8?B?bmZqw7Zyw7A=?= Bjarmason"'s message of "Mon, 10 May 2021 13:04:48 +0200") Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> writes: >>> It would have been a stronger argument to favor --new if we had "git >>> branch --new <branchname>", but that is not the case. >> >> The argument is that switch's experimental design squats on 2x other >> options, so changing -c to -n so we can make -c and -m do the same thing >> is better. > > Whatever the merit of the argument I'm putting forward here, it would be > useful to get some idea of whether you'd be categorically opposed to > changing the interface of switch/restore in breaking ways even though > they've been marked as "THIS COMMAND IS EXPERIMENTAL". > > Of course any series to implement what I suggested in > <email@example.com> would need to stand on its own > merits. > > I'm not planning on working on that since I expect the response will be > at best "neat, but that ship has sailed", but if that's not the case... cf. <firstname.lastname@example.org> "Randall S. Becker" <email@example.com> writes: >>Which leaves us with two hard choices regarding switch/restore, none of them >>really being comfortable: >> >>- we scrap switch/restore because their usability is not really all that >> improved relative to `git checkout`. > > Please do not do that. Switch/restore is much easier to understand > for new users. The semantics are also more consistent with what > others have done with git over the years anyway (EGit as an > example). I have users who have transitioned because the commands > make sense. They have not hit any missing bits in their workflows. > >>- we leave switch/restore as-are (because by now, changing the options or >> the design would be almost certainly disruptive to users who already >> tried to adopt the new commands, I being one of those users). > > I think we should work on the commands to cover between them > (well... and reset) to functionally cover what checkout > does. Leaving them as-is, I think is not a viable option. People > do know these are experimental and not to use in scripts - we can > hope anyway. Yeah, I tend to agree with you that the third-choice to improve switch/restore before we can confidently say they are no longer "experimental" would be much nicer than giving up on them too early.
next prev parent reply other threads:[~2021-05-10 18:28 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 [this message] 2021-05-06 11:00 ` Felipe Contreras 2021-05-06 15:26 ` Ævar Arnfjörð Bjarmason 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 \ --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).