Jeff King <[email protected]> writes: > Junio, Johannes: I don't know if there were particular plans to pick up > those getenv() fixes for "maint", but if we're going to do a v2.20.2, it > might be worth it. It's also possible that it's just due to ca1b411648 > (mingw: safe-guard a bit more against getenv() problems, 2019-02-15), > but I'd consider that to be maint-worthy as well. > > It may be that we just don't do a v2.20.2, though, since v2.21 is so > close to release.
Yeah, they are all low-risk and straight-forward changes, and were queued on a topic branch forked at 2.19.2 to make it possible to directly merge to older maintenance tracks. So if we are going to update 2.20.x (or even 2.19.x) series, we can certainly include them. Thanks.
