There are a couple of problems with this function: - premature design - create "gitdir" file outside multi-worktree context - update the file's content with relative path, with breaks "worktree list" The first three patches kill it, as a result. They are relatively safe. The last three re-implement it in a new form, "worktree refresh", inspired by "update-index --refresh". For now the user can use this command to correct some internal data after moving a worktree. In future, we might do automatic refresh like we do with the index. The last three try out new design, so it will probably take more time to graduate than the first three, which may end up in the next release as worktree bug fix. Eric Sunshine (1): worktree.txt: how to fix up after moving a worktree Nguyễn Thái Ngọc Duy (5): worktree.c: fix indentation worktree: stop supporting moving worktrees manually abspath.c: add and use real_path_dup() setup.c: record the location of .git file worktree: new command to fix up worktree's info after moving Documentation/git-worktree.txt | 21 ++++++++++++++++----- abspath.c | 5 +++++ builtin/clone.c | 2 +- builtin/init-db.c | 6 +++--- builtin/worktree.c | 18 ++++++++++++++++++ cache.h | 2 ++ setup.c | 26 +++++++++++--------------- t/t1501-worktree.sh | 9 +++++++++ worktree.c | 8 ++++---- 9 files changed, 69 insertions(+), 28 deletions(-) -- 2.7.0.96.g5373197 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html