On Wed, Apr 13, 2016 at 2:54 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Hmph, isn't this already in 'next', hence we cannot accept a > replacement patch? Yes, this is already in 'next'. This was going to be merged in the third cycle after 2.8 but on my request, you delayed it. So this is an update on the patch. Is it that once a patch is in 'next', it cannot be replaced with a new updated one? There are 5 other patches along with this which are a requirement for this patch. -- 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