git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Namikaze Minato <LLoydsensei+git@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-switch history and checkout compatibility
Date: Tue, 01 Aug 2023 11:28:47 -0700	[thread overview]
Message-ID: <xmqqleeubork.fsf@gitster.g> (raw)
In-Reply-To: <CACmJb3wTsWdqDGrkYC0p+eB-XYBotVcFAKcXJF3ftYdiiRvEdw@mail.gmail.com> (Namikaze Minato's message of "Tue, 1 Aug 2023 19:23:20 +0200")

Namikaze Minato <LLoydsensei+git@gmail.com> writes:

> Isn't checkout supposed to become deprecated at some point?

Deprecating "checkout" hurts those who are confused by what the
split "switch/restore" pair of commands do (cf. this very discussion
we are having), and folks who are happily using "checkout".  On the
other hand, those who are happy with "switch/restore" would not be
affected by the existence of "checkout".  So, no, I do not think it
is part of the map to deprecate the command.  At least not until the
split "switch/restore" pair of commands become less confusing and
lose their "experimental" state, that is.

> ... And as you said you were
> not among the primary advocates to add it, I guess we should wait for
> someone else to reply about this?

There are things "switch/restore" pair do differently relative to
"checkout".  Some of them (like "restore" allowing checking out
paths from tree only to the working tree files while not touching
the index, which is not possible with "checkout") are very much
welcome improvement, but some others (cf. this very discussion we
are having on "switch") may simply not make any sense.  Those who
advocated and pushed the split "switch/restore" pair should be able
to explain why they chose to do things differently much better than
I would be (some differences may simply be bugs waiting to be fixed
by them).

      reply	other threads:[~2023-08-01 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACmJb3yoHagaU1wb4qRT-nZV4Wptao8boaUXCAYrFxfrxcmUYg@mail.gmail.com>
2023-06-28 13:03 ` git-switch history and checkout compatibility Namikaze Minato
2023-06-28 16:39   ` Junio C Hamano
2023-08-01 17:23     ` Namikaze Minato
2023-08-01 18:28       ` 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=xmqqleeubork.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=LLoydsensei+git@gmail.com \
    --cc=git@vger.kernel.org \
    /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).