Re: [PATCH 2/2] setup.c: re-fix d95138e (setup: set env $GIT_WORK_TREE when ..

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH 2/2] setup.c: re-fix d95138e (setup: set env $GIT_WORK_TREE when ..

From: Junio C Hamano <hidden>
Date: 2016-06-15 23:07:22

Nguyễn Thái Ngọc Duy  [off-list ref] writes:
... Now I conclude
that setup-messed-by-alias is always evil. So the env restoration is
done for _all_ commands  whenever aliases are involved.
So a side effect of this is whenever an alias is involved, all
commands are re-spawned, not just the external ones but builtins as
well.
 This may be a brilliant fix, or another invitation for regressions.
;-)

Re: [PATCH 2/2] setup.c: re-fix d95138e (setup: set env $GIT_WORK_TREE when ..

From: Duy Nguyen <hidden>
Date: 2016-06-15 23:07:23

On Fri, Dec 4, 2015 at 9:35 PM, Junio C Hamano [off-list ref] wrote:
Nguyễn Thái Ngọc Duy  [off-list ref] writes:
quoted
... Now I conclude
that setup-messed-by-alias is always evil. So the env restoration is
done for _all_ commands  whenever aliases are involved.
So a side effect of this is whenever an alias is involved, all
commands are re-spawned, not just the external ones but builtins as
well.
I missed that while re-reading c056261, but yes that's true. So
Windows folks will be grumpy anyway. Maybe we can avoid that in
certain (safe) cases, when we know the second setup_git_... will be
executed by the builtin command and won't have any side effects, which
is probably the common case. But let's see how it goes.
-- 
Duy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help