ation option that
would take precedence for doing note rewrites for the given ref (like how
`notes..mergeStrategy` takes precedence for merges).
Regards,
Barret Rennie
ption that
would take precedence for doing note rewrites for the given ref (like how
`notes..mergeStrategy` takes precedence for merges).
Regards,
Barret Rennie
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More ma
.org/gmane.comp.version-control.git/298194
Yes, it does seem like `git worktree move` will solve all my issues and
is a much more elegant solution. Thanks for pointing it out to me and
looking at this patch.
I may write a patch to print out the worktree tag name instead and submit
that later.
Reg
> On Jun 26, 2016, at 5:00 PM, Eric Sunshine wrote:
>
> On Sat, Jun 25, 2016 at 3:45 PM, Junio C Hamano wrote:
>> [...snip...]
>> And explained that way, it becomes clearer that you would want to
>> name $HOME/xyzzy-1/frotz worktree after "topic-1", not the default
>> name you would get "frotz"
> On Jun 26, 2016, at 12:15 PM, Junio C Hamano wrote:
>
> Junio C Hamano writes:
>
>> Now, if you do the worktree, you may still want the relative
>> structure between these two, i.e. if you want to work on two
>> different branch combinations of the whole thing, you would want to
>> do this:
> On Jun 25, 2016, at 1:45 PM, Junio C Hamano wrote:
>
> Barret Rennie writes:
>
>>> 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'?
>>
>> Th
Sorry for replying to that message twice. I hit a bug in Apple Mail.
--Barret
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> 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 argument?
Currently, if you run:
> 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 argument?
Currently, if you run:
, reviewboard1, reviewboard2, etc. it is that
I’ve broken, instead of being able to just go into the worktree named for the
release branch.
Hope this clarifies things.
> On Jun 25, 2016, at 12:17 AM, Junio C Hamano wrote:
>
> Barret Rennie writes:
>
>> Add the --name paramet
Add the --name parameter to git worktree add that allows the user to set
the name of the created worktree directory. A worktree must not already
exist with the current name or creation will fail.
Signed-off-by: Barret Rennie
---
Documentation/git-worktree.txt | 6 +-
builtin/worktree.c
11 matches
Mail list logo
