From: Barret Rennie <barret@brennie.ca>
To: Johannes Sixt <j6t@kdbg.org>
Cc: git@vger.kernel.org, "Eric Sunshine" <sunshine@sunshineco.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Michael Rappazzo" <rappazzo@gmail.com>
Subject: Re: [PATCH] builtin/worktree.c: add option for setting worktree name
Date: Sat, 25 Jun 2016 01:29:49 -0600 [thread overview]
Message-ID: <1FEF5F90-6534-4D91-B27C-16FE6D16EC3F@brennie.ca> (raw)
In-Reply-To: <576E2FA9.7070008@kdbg.org>
> What is "the name for the worktree"? Is it the directory where it lives in?
>Is it how it is listed with 'git worktree list'?
The name of the worktree is the name of the created directory in
`.git/worktrees`.
> How is --name different from the <path> argument?
Currently, if you run:
git worktree add /my/worktree/checkout <branch>
you get a worktree "named" checkout, i.e., `.git/worktrees/checkout`. The
idea with this patch is to allow you use a more specific name when you would
otherwise have mulitiple worktrees of the form `checkout`, `checkout1`, etc.
That is, you could do
git worktree add --name branch1 /worktrees/branch1/src branch1
git worktree add --name branch2 /worktrees/branch2/src branch2
git worktree add --name branch3 /worktrees/branch3/src branch3
and have `.git/worktrees/branch1`, `.git/worktrees/branch2` and
`.git/worktrees/branch3` instead of `.git/worktrees/src`,
`.git/worktrees/src1`, `.git/worktrees/src2`. That way, it becomes more clear
when poking inside `.git/worktrees` which directory points to which checkout.
Perhaps "worktree name" isn't the most clear nomenclature for this feature.
Would "worktree directory name" be better?
next prev parent reply other threads:[~2016-06-25 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 5:15 [PATCH] builtin/worktree.c: add option for setting worktree name Barret Rennie
2016-06-25 6:17 ` Junio C Hamano
2016-06-25 6:28 ` Barret Rennie
2016-06-25 7:15 ` Johannes Sixt
2016-06-25 7:29 ` Barret Rennie
2016-06-25 7:29 ` Barret Rennie [this message]
2016-06-25 19:45 ` Junio C Hamano
2016-06-25 20:19 ` Barret Rennie
2016-06-26 18:15 ` Junio C Hamano
2016-06-27 5:40 ` Barret Rennie
2016-06-27 13:17 ` Junio C Hamano
2016-06-26 23:00 ` Eric Sunshine
2016-06-27 5:52 ` Barret Rennie
2016-06-27 23:11 ` Eric Sunshine
2016-06-29 4:45 ` Barret Rennie
2016-06-25 7:32 ` Barret Rennie
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=1FEF5F90-6534-4D91-B27C-16FE6D16EC3F@brennie.ca \
--to=barret@brennie.ca \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=pclouds@gmail.com \
--cc=rappazzo@gmail.com \
--cc=sunshine@sunshineco.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).