git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Junio C Hamano <gitster@pobox.com>,
	Kristoffer Haugsbakk <code@khaugsbakk.name>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Revert "Declare both git-switch and git-restore experimental"
Date: Tue, 20 Feb 2024 19:39:33 +0100	[thread overview]
Message-ID: <0174d19e-abc4-4d2e-a60d-e7df52b74d0b@kernel.org> (raw)
In-Reply-To: <xmqqzfvvovva.fsf@gitster.g>

Hi Junio,

Thank you for your reply!

On 20/02/2024 7:04 pm, Junio C Hamano wrote:
> "Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:
> 
>> The only reason why I ask is because I was vaguely aware of some
>> discussions (don’t know how long ago) where someone was skeptical about
>> changing one of the two experimental commands, and then someone else in
>> turn expressed some frustration about this concern since they are after
>> all marked experimental. And the context was some UI/UX problems with
>> the command.
> 
> There was a discussion to further make "switch" deviate from
> "checkout" by taking advantage of its experimental status [*1*], for
> example.

I appreciate the references, thank you! It is interesting to note
changes have been proposed a few years ago, but none have been applied.

> Being marked as "EXPERIMENTAL" allows us to redefine the behaviour
> in a way that would break existing users, like changing what the
> "-c" option means completely (so that folks who are used to say
> "switch -c blah" will be surprised next time they type that command,
> but they cannot complain).

Personally, I think I would complain, and go back to git-checkout :-)

> Once you remove the label, you no longer
> have such a freedom to even imagine departing from the existing
> behaviour (I wrote essentially the same thing before [*2*]).  Are we
> ready to paint us into such a corner yet?

I'm not involved in this project, but I think after a few versions /
years, it is hard to still keep this experimental status. I understand
it is tempting to keep it, but I think it is now too late. Despite the
now old label, you probably already no longer have such freedom to
radically change their behaviours, no?

> Is "switch/restore" perfect
> and do not need departing changes anymore?
To me, they don't need departing changes. If they are still experimental
after 5 years, it is hard to recommend them :)

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.

  reply	other threads:[~2024-02-20 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20  9:29 [PATCH] Revert "Declare both git-switch and git-restore experimental" Matthieu Baerts (NGI0)
2024-02-20  9:36 ` Kristoffer Haugsbakk
2024-02-20  9:58   ` Matthieu Baerts
2024-02-20 11:36     ` Kristoffer Haugsbakk
2024-02-20 18:04       ` Junio C Hamano
2024-02-20 18:39         ` Matthieu Baerts [this message]
2024-02-20 19:57         ` Martin
2024-02-20 13:34   ` Martin
     [not found]   ` <dfaed16c-5e24-4dfb-8afd-b703134e5ada@mfriebe.de>
2024-02-20 16:20     ` Kristoffer Haugsbakk

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=0174d19e-abc4-4d2e-a60d-e7df52b74d0b@kernel.org \
    --to=matttbe@kernel.org \
    --cc=code@khaugsbakk.name \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@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 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 NNTP newsgroup(s).