From: Paul Smith <paul@mad-scientist.net>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.16.0-rc0
Date: Thu, 04 Jan 2018 16:35:53 -0500 [thread overview]
Message-ID: <1515101753.2717.690.camel@mad-scientist.net> (raw)
In-Reply-To: <20180104201804.GE2641@hank>
On Thu, 2018-01-04 at 20:18 +0000, Thomas Gummerer wrote:
> On 12/29, Paul Smith wrote:
> > On Thu, 2017-12-28 at 20:30 -0800, Junio C Hamano wrote:
> > > * The way "git worktree add" determines what branch to create
> > > from where and checkout in the new worktree has been updated a
> > > bit.
> >
> > Does this include the enhancements published a few weeks ago to
> > allow worktrees to be created directly from remote branches without
> > first checking out the branch locally? I'm really looking forward
> > to that change...
>
> Yes, this release will include that. It would be awesome if you
> could test the rc, now is the best time to scream if something about
> it is not as you'd expect :)
OK, I pulled and built this locally, and indeed the straightforward
"git worktree add <path> <branch>" works just as I'd hoped! Nice!
I'll play with it more and let you know if I hit issues.
next prev parent reply other threads:[~2018-01-04 21:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 4:30 [ANNOUNCE] Git v2.16.0-rc0 Junio C Hamano
2017-12-29 7:17 ` Kaartic Sivaraam
2017-12-29 17:13 ` Paul Smith
2018-01-04 20:18 ` Thomas Gummerer
2018-01-04 21:35 ` Paul Smith [this message]
2018-01-03 3:34 ` Bryan Turner
2018-01-03 5:07 ` Jonathan Nieder
2018-01-03 5:41 ` Bryan Turner
2018-01-03 5:50 ` Jonathan Nieder
2018-01-03 21:15 ` Junio C Hamano
2018-01-03 5:35 ` Jonathan Nieder
2018-06-08 4:50 ` Jeff King
2018-06-12 16:29 ` Junio C Hamano
2018-06-14 18:30 ` Jeff King
2018-06-14 18:55 ` Jonathan Nieder
2018-06-14 19:39 ` Jeff King
2018-06-15 4:20 ` Jonathan Nieder
2018-06-15 5:13 ` Jeff King
2018-06-15 7:26 ` Jeff King
2018-01-04 20:33 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1515101753.2717.690.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=git@vger.kernel.org \
--cc=t.gummerer@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).