On Tue, Dec 22, 2015 at 1:31 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx> writes: >> >>> This commit has caused three regression reports so far. All of them are >>> about spawning git subprocesses, where the new presence of GIT_WORK_TREE >>> either changes command behaviour (git-init or git-clone), or how >>> repo/worktree is detected (from aliases), with or without $GIT_DIR. >>> The original bug will be re-fixed another way. >>> >>> Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx> >>> --- >>> On Thu, Dec 3, 2015 at 12:09 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >>> > OK, when/if you decide that our first step should be a revert of >>> > d95138e please send in a patch to do so with a brief write-up of a >>> > follow-up plan. >>> >>> Three reports to me are enough. And I obviously could not push the >>> fix out fast enough. So if you want to revert it, here's the patch on >>> maint. > > Also, can you reference these three reports for future reference? http://article.gmane.org/gmane.comp.version-control.git/281608 http://article.gmane.org/gmane.comp.version-control.git/281979 http://article.gmane.org/gmane.comp.version-control.git/282691 The last one is not confirmed by the reporter yet. But I'm pretty sure i'll trigger the special case "when GIT_WORK_TREE is set but GIT_DIR is not" in setup code -- Duy -- 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