Duy Nguyen [off-list ref] writes:
On Fri, Jul 17, 2015 at 7:27 PM, Michael J Gruber
[off-list ref] wrote:
quoted
Two more observations:
$ git worktree add /tmp/gitwt
Enter /tmp/gitwt (identifier gitwt)
Switched to a new branch 'gitwt'
Now I'm in /tmp/gitwt at branch gitwt. Right? No. I'm in the original wd
at the original branch.
So either we cd to the new location or quelch these messages or add a
message that we're actually back.
s/Enter/Preparing/ ?
Hmm, do we even need that message? I assumed it was a leftover
debugging stuff ;-)
On Fri, Jul 17, 2015 at 11:19 AM, Junio C Hamano [off-list ref] wrote:
Duy Nguyen [off-list ref] writes:
quoted
On Fri, Jul 17, 2015 at 7:27 PM, Michael J Gruber
[off-list ref] wrote:
quoted
Two more observations:
$ git worktree add /tmp/gitwt
Enter /tmp/gitwt (identifier gitwt)
Switched to a new branch 'gitwt'
Now I'm in /tmp/gitwt at branch gitwt. Right? No. I'm in the original wd
at the original branch.
So either we cd to the new location or quelch these messages or add a
message that we're actually back.
s/Enter/Preparing/ ?
Hmm, do we even need that message? I assumed it was a leftover
debugging stuff ;-)
It helps give context to messages which follow it, such as "Checking
out files:..." and "HEAD is now at...", letting the user know that
those messages apply to the new worktree rather than the current one.
In this case, s/Enter/Preparing/ makes sense.
("Switched to a new branch..." is gone in 'pu'.)