From: Jeff King <peff@peff.net>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: 'Junio C Hamano' <gitster@pobox.com>,
'Christian Couder' <christian.couder@gmail.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2019, #06; Thu, 25)
Date: Fri, 9 Aug 2019 12:29:01 -0400 [thread overview]
Message-ID: <20190809162900.GA9094@sigill.intra.peff.net> (raw)
In-Reply-To: <001e01d54ebb$9a1ab4b0$ce501e10$@nexbridge.com>
On Fri, Aug 09, 2019 at 10:06:06AM -0400, Randall S. Becker wrote:
> 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.
I don't know of any plans for checkout in particular, but I think the
docs for restore/switch make it clear that it's way too early to start
scripting around them:
$ git grep EXPERIMENTAL Documentation/
Documentation/git-restore.txt:THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.
Documentation/git-switch.txt:THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.
-Peff
next prev parent reply other threads:[~2019-08-09 16:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 0:19 What's cooking in git.git (Jul 2019, #06; Thu, 25) Junio C Hamano
2019-07-26 14:33 ` Johannes Schindelin
2019-07-26 20:23 ` Junio C Hamano
2019-07-27 19:38 ` Rohit Ashiwal
2019-07-27 20:40 ` Elijah Newren
2019-07-27 20:57 ` Rohit Ashiwal
2019-07-27 21:42 ` Elijah Newren
2019-07-28 20:34 ` Carlo Arenas
2019-08-09 0:13 ` Taylor Blau
2019-08-09 1:34 ` Ariadne Conill
2019-08-09 2:07 ` Taylor Blau
2019-08-09 3:04 ` Ariadne Conill
2019-08-09 3:07 ` Phil Hord
2019-08-09 3:21 ` Ariadne Conill
2019-08-09 11:21 ` Taylor Blau
2019-08-09 11:41 ` Jeff King
2019-08-09 17:39 ` Phil Hord
2019-08-09 14:06 ` Randall S. Becker
2019-08-09 16:29 ` Jeff King [this message]
2019-08-09 16:32 ` Randall S. Becker
2019-08-09 17:45 ` Junio C Hamano
2019-08-09 18:05 ` Phil Hord
2019-08-10 6:10 ` Jeff King
2019-08-12 0:39 ` Junio C Hamano
2019-08-12 13:39 ` Randall S. Becker
2019-08-09 17:44 ` Junio C Hamano
2019-08-09 19:06 ` Randall S. Becker
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=20190809162900.GA9094@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rsbecker@nexbridge.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).