On 04/19, Eric Wong wrote:
> Johannes Sixt wrote:
> > Am 19.04.2017 um 01:18 schrieb Brandon Williams:
> > >@@ -400,6 +404,53 @@ static char **prep_childenv(const char *const
> > >*deltaenv)
> > > }
> > > #endif
> > >
> >
> > Does this #endif in this hunk context belong to an #ifndef
> > GIT_WIN
Johannes Sixt wrote:
> Am 19.04.2017 um 01:18 schrieb Brandon Williams:
> >@@ -400,6 +404,53 @@ static char **prep_childenv(const char *const *deltaenv)
> > }
> > #endif
> >
>
> Does this #endif in this hunk context belong to an #ifndef
> GIT_WINDOWS_NATIVE? If so, I wonder why these new function
Am 19.04.2017 um 01:18 schrieb Brandon Williams:
@@ -400,6 +404,53 @@ static char **prep_childenv(const char *const *deltaenv)
}
#endif
Does this #endif in this hunk context belong to an #ifndef
GIT_WINDOWS_NATIVE? If so, I wonder why these new functions are outside
these brackets? An over
From: Eric Wong
Signal handlers of the parent firing in the forked child may
have unintended side effects. Rather than auditing every signal
handler we have and will ever have, block signals while forking
and restore default signal handlers in the child before execve.
Restoring default signal h
4 matches
Mail list logo