| commit | 618244e160cb0777bc8d41055f7de0192b10ea0f | |
| author | Nguyễn Thái Ngọc Duy <pclouds@gmail.com> | |
| Fri, 22 Jan 2016 08:35:49 +0000 (22 15:35 +0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 22 Jan 2016 22:28:42 +0000 (22 14:28 -0800) | ||
| tree | b414b7f5842a0b09ac307982a190649aa8492c0b | treesnapshot (tar.gz zip) |
| parent | d4cddd66d7ab620fe449ab01382b27178c908c10 | commitdiff |
worktree: stop supporting moving worktrees manually
The current update_linked_gitdir() has a bug that can create "gitdir"
file in non-multi-worktree setup. Worse, sometimes it can write relative
path to "gitdir" file, which will not work (e.g. "git worktree list"
will display the worktree's location incorrectly)
Instead of fixing this, we step back a bit. The original design was
probably not well thought out. For now, if the user manually moves a
worktree, they have to fix up "gitdir" file manually or the worktree
will get pruned.
Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The current update_linked_gitdir() has a bug that can create "gitdir"
file in non-multi-worktree setup. Worse, sometimes it can write relative
path to "gitdir" file, which will not work (e.g. "git worktree list"
will display the worktree's location incorrectly)
Instead of fixing this, we step back a bit. The original design was
probably not well thought out. For now, if the user manually moves a
worktree, they have to fix up "gitdir" file manually or the worktree
will get pruned.
Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-worktree.txt | diffblobblamehistory | |
| setup.c | diffblobblamehistory |