Re: What's cooking in git.git (Jul 2019, #06; Thu, 25)

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 9, 2019, 17:44 UTC
Message-ID: <xmqq7e7mdyig.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <001e01d54ebb$9a1ab4b0$ce501e10$@nexbridge.com>

"Randall S. Becker" <rsbecker@nexbridge.com> writes:

Show 11 quoted lines

> On 01 Aug 2019 13:05:12, Junio wrote:
>> >> *snip*
>
> I think this got missed in the shuffle, but I am getting questions
> about the topic from my own team that I cannot answer.
>
> I noticed that the switch and restore commands are now available
> in 2.23.0 but are not discussed in recent What's Cooking or Git
> Rev (or I blithely missed them). The question from my team is what
> are the plans for deprecating checkout. They have loads of scripts
> and want to plan for moving over.

The two new commands were done in response to a common "checkout does two different things, either checkout a branch in order to start working on it, or checkout paths into the current workspace to work on them" complaint. Those who are used to and are OK with the "git" command that changes behaviour based on the rest of args (i.e. "checkout <branchname>" and "checkout [<tree-ish>] <pathspec>" are the ways to obtain these two behaviours) can safely keep using the command they are familiar with.

I do not think there currently is any plan to deprecate checkout.