Jeff King fb9c2d2703 refs: use chdir_notify to update cached relative paths ... Commit f57f37e2e1 (files-backend: remove the use of git_path(), 2017-03-26) introduced a regression when a relative $GIT_DIR is used in a working tree: - when we initialize the ref backend, we make a copy of get_git_dir(), which may be relative - later, we may call setup_work_tree() and chdir to the root of the working tree - further calls to the ref code will use the stored git directory, but relative paths will now point to the wrong place The new test in t1501 demonstrates one such instance (the bug causes us to write the ref update to the nonsense "relative/relative/.git"). Since setup_work_tree() now uses chdir_notify, we can just ask it update our relative paths when necessary. Reported-by: Rafael Ascensao <rafa.almas@gmail.com> Helped-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>		2018-03-30 12:50:03 -07:00
..
files-backend.c	refs: use chdir_notify to update cached relative paths	2018-03-30 12:50:03 -07:00
iterator.c	prefix_ref_iterator: break when we leave the prefix	2017-09-14 15:19:07 +09:00
packed-backend.c	refs: use chdir_notify to update cached relative paths	2018-03-30 12:50:03 -07:00
packed-backend.h	files-backend: don't rewrite the `packed-refs` file unnecessarily	2017-10-30 09:45:15 +09:00
ref-cache.c	Use MOVE_ARRAY	2018-01-22 11:32:51 -08:00
ref-cache.h	ref_cache: remove support for storing peeled values	2017-09-25 18:02:46 +09:00
refs-internal.h	refs: update some more docs to use "oid" rather than "sha1"	2017-11-06 10:31:08 +09:00