On Sun, Feb 28, 2016 at 12:34 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > We'd still want the fixes to apply on top of relevant topics if we > could, as the fix to the topic itself (with or without i18n fixes), > when we discover that it has a huge flaw not desirable in v2.8.0, > might be to revert the whole thing, though. > >> I'm not >> sure if there's enough time for translators before release though. > > Also we need to get an Ack from the authors of commits we added in > this cycle that these patches fix i18n bugs they introduced and make > sure there is no "this i18n mark is not appropriate as it is a > plumbing output (or protocol messsage) that should not be > translated" response from them. It won't be like I apply these > blindly today and ask translators to start working. Urgh.. if there are only a handful of topics (like in 'pu' and 'next' now), I could go identify author/series manually. But there are 118 topics since 2.7.2 and my series changes about 300 strings. Hold on tight, let me write something that blames based on diff... -- Duy -- 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
