Jeff King <peff@xxxxxxxx> writes: > On Fri, Mar 04, 2011 at 09:16:30AM -0800, Junio C Hamano wrote: > >> How prevalent is the problematic cygwin1.dll 1.7.8? Also for how long did >> this bug exist, in other words, if we were to make a table of problematic >> versions, would we have only just a handful entries in it? Also can we at >> runtime find out what version we are running? >> >> The reason I am asking these questions is because I think, assuming that >> ... > How are we doing the runtime test for platform max write? I asked (1) if we can find out at runtime if we are on which version of cygwin1.dll, and (2) if we can have a small list of "bad" versions of cygwin1.dll. If both are true, the runtime test should be trivial, no? > So I think the test needs to be "is our version of cygwin in the broken > list" and not "let's try a few different writes and see what works". Yes, that is exactly what I had in mind. -- 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