All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Andy Koppe <andy.koppe@gmail.com>,
	 git@vger.kernel.org,  pclouds@gmail.com
Subject: Re: [PATCH] checkout: add config variable checkout.autoDetach
Date: Tue, 14 Nov 2023 09:48:19 +0900	[thread overview]
Message-ID: <xmqq7cml2m98.fsf@gitster.g> (raw)
In-Reply-To: <0e37ee23-922c-4bbf-82c3-8f44e9216ab0@gmail.com> (Phillip Wood's message of "Mon, 13 Nov 2023 15:07:15 +0000")

Phillip Wood <phillip.wood123@gmail.com> writes:

>> and good thing to help new users.  I do not know how others react to
>> this kind of proliferation of configuration variables, but I do not
>> mind this particular variable existing.
>
> I'm a bit wary of having a config variable that could break
> scripts relying on the current behavior of "git checkout".  As far
> as "git switch" goes I don't particularly mind this config
> variable though I'm not sure it is that hard to type "--detach"
> (especially with tab completion) and

I do not have much sympathy myself to scripts that are not being
defensive enough to write "--detach" explicitly, but I do understand
and share your concern as the project maintainer.

> ... I do worry that we're making the UI more complex each
> time we add something like this.

Thanks for saying this---this is exactly the kind of reaction I as
expecting to see.

>
> Best Wishes
>
> Phillip

      reply	other threads:[~2023-11-14  0:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11 22:42 [PATCH] checkout: add config variable checkout.autoDetach Andy Koppe
2023-11-12  6:04 ` Junio C Hamano
2023-11-12  9:15   ` Andy Koppe
2023-11-13 15:07   ` Phillip Wood
2023-11-14  0:48     ` Junio C Hamano [this message]

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=xmqq7cml2m98.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=andy.koppe@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=phillip.wood123@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.