On Sun, Oct 29, 2017 at 8:36 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Jacob Keller <jacob.keller@xxxxxxxxx> writes: > >> I am pretty confident we can fix it.... > > I am sure we can eventually, but 3 hours is not enough soak time. > > I am inclined to leave the fix for 2.15.1/2.16.0 instead of delaying > the release by 10 more days. That's fair. I'm not even sure it was introduced since the last release (I tried 2.12, but not 2.13 or 2.14 manually). Thus, it likely wasn't noticed for at least a release, meaning it's less important (to me at least) that we provide a fix immediately, since it went unnoticed this long, likely that means few people will be impacted. As far as I can tell, you'd only be impacted if you attempt to run a git command from within a sub directory inside of an exec statement. Is there some place we can list it as a known bug in case someone else runs into it? Regards, Jake
