Hi Junio, On Wed, 13 Jul 2016, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > > This was just a quick fix, intended to allow me to release Git for Windows > > v2.9.1 in a timely manner (which is now delayed for other reasons). > > ... > >> You'll need to adjust check_show as I did in my earlier patch. > > > > Makes sense! > > Hmph, so what is your preferred approach? You'll do your own v2.9.1 > that is different from others at t0006? I may do a Git for Windows v2.9.1 that is different from Git v2.9.1 in t0006, yes. Git for Windows still has tons of patches on top of Git because I seem to be unable to drain the patch queue as fast as I want, so I do not believe it is a big deal. > I was hoping to hear from you sooner and do v2.9.2 with your t0006 > workaround with lazy-prereq changes from Peff (i.e. "Makes sense!" > above), so that you do not have to do two releases in a row > (i.e. skipping v2.9.1 saying "Git for Windows skipped that one > because it was not quite right; this release fixes the issue" in > your v2.9.2 announcement). I am sorry that you expected me to be more available. It is a pretty crazy week already (and trying to get a Git for Windows v2.9.1 out of the door after dropping everything else on Tuesday morning added quite a bit to the load), so I am at times unable to even read the Git mailing list. As I am more concerned with Jeff Hostetler's patch now (the "very verbose porcelain status"; I merged the Pull Request after seeing no comments on his mail, but then Peff provided some good feedback, so now I am not quite certain how to go about it: revert, or wait if the 2nd iteration is acceptable and take that), so I am not immediately releasing any version, anyway. Ciao, Dscho -- 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