> On Jun 26, 2016, at 5:00 PM, Eric Sunshine <[email protected]> wrote: > > On Sat, Jun 25, 2016 at 3:45 PM, Junio C Hamano <[email protected]> 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" (because the default gives you the leaf >> level name of the newly created worktree). >> >> After the discussion above (which may or may not match what you >> raised this topic for), I think a feature to let you override the >> default name makes sense. > > One thing which hasn't been explained, and about which I'm still > confused even after reading this thread in its entirety, is what > Barret means when he says that he "breaks" his worktrees. What is the > nature of this breakage? Depending upon that answer, would "git > rev-parse --git-dir" be sufficient for your needs? Or, would "git > worktree list" be able to give you the desired information? (As > envisioned, "git worktree list" was intended to provide much more > information than it currently does, such as the .git/worktree dir > name, and such an enhancement might be welcome.)
My worktree breakages are usually the result of my reorganizing my projects, usually because a branch changes name (for example, if branch release-1 gets pushed back to release-2). Then I go and rename all my directories and git gets unhappy and I have to manually fix them or re-create the worktrees. Having `git worktree list` give the worktree directory would be very useful, but I still would like the ability to change the name of a worktree. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
