Re: Cooking of the ab/i18n series

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 6, 2010, 23:01 UTC
Message-ID: <7viq3n73c6.fsf@alter.siamese.dyndns.org>
In-Reply-To: <AANLkTik1KVpb25nuwSFA2z4ezRJKWdTwRrS_KXzwM+2D@mail.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

Show 15 quoted lines

> My mental plan for this series has basically been as follows:
>
>   1. Get it to a state where it can cook in pu [You Are Here]
>
>   2. After it's been there for a while get it to master
>
>   3. Once it's there for a while and we're sure the new dependency /
>      code doesn't harm some more obscure systems..
>
>   4. Start submitting patches to the main porcelain $(grep
>      'mainporcelain common' command-list.txt) to make the most common
>      user-visible messages translatable.
>
>   5. Recruit translators to translate the strings in #4. Send
>      translations in as patches adding/altering the *.po files.

Matches my expectations modulo s/master/next/. The stuff parked in 'pu' was primarily because most of the work to get to this point was done during the pre-release freeze for 1.7.2 and I didn't want to get distracted, while I obviously did not lose patches.

> Now, your main concern is that this doesn't break plumbing output....

That's not 'main'.

'Breaking plumbing' is merely an example of a larger 'main concern' which is 'unintended consequences'.

And please don't ask me to enumerate them exhaustively. By definition 'unintended consequences' cannot be enumerated. They are discovered over time either by code inspection, by people guinea-pigging a version outside 'master', and by careful thinking.