Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes: > Pranit Bauva <pranit.bauva@xxxxxxxxx> writes: > >> ================================= SUMMARY ================================== >> My micro project on adding config variable to git-commit for verbose options >> is going to be merged with the master branch soon and will be available for >> git 2.8.3 . > > Nit: being merged to master doesn't mean you'll be in the next minor > release, but in the next _major_ one. 2.8.3 will only contain bugfixes > compared to 2.8.2. Correct. Recent "What's cooking" lists the topic as "Will merge to 'master'" but this does not promise in which timeframe it will be merged to 'master', so it may not even be in 2.9.0 at all. Generally, what is in 'next' is marked as "Will merge to 'master'" by default, until a reason not to do so is found, at which time the mark is changed to "Will hold", etc., so saying "master branch soon" upon seeing "Will merge to 'master'" is a bit of overstatement. In fact, "git log maint..pb/commit-verbse-config" shows that this new feature is not ineligible for the maintenance track. It will never be in 2.8.3 or any 2.8.x series. -- 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