On Thu, May 26, 2016 at 09:37:19AM -0700, Junio C Hamano wrote: > >> There was no particular "caveat" raised there to recommend against > >> using this on particular versions of tools or platforms. It was > >> inertia that has kept the new optional feature "optional". > > > > Thanks for digging. That matches my recollection and the limited > > research I did more recently. > > For completeness's sake I should point out that the discussion on > the first thread did point out some version-dependent issues. But > with 79c461d5 (docs: default to more modern toolset, 2010-11-19), we > declared the problematic versions obsolete; I suspect that it is > safe to assume that those who would be hurt by flipping the default > would already be extinct after 6 years since then.
Yeah, I'd agree, though that may be worth mentioning in the commit message. > > OK. I was trying to see if (1) could be low-hanging fruit for any of the > > newcomers, but at this point it probably makes sense for you to just > > write the patch. > > Leaving it as low-hanging fruit is actually a good idea. > > I was thinking about flipping it in Meta/dodoc.sh, which would > update the git-manpages.git repository whose mirrors are found at Ah, right. I was thinking that the patch would go to "master" first, but there is no reason it could not be flipped independently for your build process. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
