From: Sergey Organov <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: Wed, 05 May 2021 22:48:14 +0300 [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 "Wed, 05 May 2021 13:09:47 +0200") Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> writes: > On Tue, May 04 2021, Elijah Newren wrote: > >> On Tue, May 4, 2021 at 3:36 AM Gábor Farkas <email@example.com> wrote: >>> >>> hi, >>> >>> the "git switch" and "git restore" commands were released two years >>> ago, but the manpage still says "THIS COMMAND IS EXPERIMENTAL. THE >>> BEHAVIOR MAY CHANGE.". >>> >>> i'd love to use them, but this warning gives me pause, perhaps i >>> should wait until it stops being experimental, i worry that it might >>> change in behavior unexpectedly and cause problems for me. >>> >>> considering that they were released two years ago, could the >>> experimental-warning be removed now? >>> >>> thanks, >>> gabor >> >> This probably makes sense. The author of switch and restore isn't >> involved in the git project anymore. He decided to work on other >> things, which was and is a big loss for us. I think others (myself >> included) didn't know all the things that might have been in Duy's >> head that he wanted to verify were working well before marking this as >> good, but these two commands have generally been very well received >> and it has been a few years. Personally, I'm not aware of anything >> that we'd need or want to change with these commands. > > I am. > [...] > And: > > # Moves a branch (or -M for --force) > git branch -m old new > > That last one we can't have either because "switch" squats on "-m" for > "--merge", which I daresay is a much more obscure use-case not deserving > of a short option than "rename and switch to". Isn't --merge a different (and inferior) way to achieve what we already have elsewhere with --autostash? Does it make sense to get rid of --merge here in favor of --autostash? Thanks, -- Sergey Organov
next prev parent reply other threads:[~2021-05-05 19:48 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 [this message] 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 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).