Re: Cooking of the ab/i18n series

["Ævar Arnfjörð Bjarmason" <avarab@gmail.com>]

On Fri, Aug 6, 2010 at 23:01, Junio C Hamano <gitster@pobox.com> wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> 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/.

Yes, I meant to say "on track to master" (via 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.

I didn't mean to rush you, the delay is fine. It just sounded like the
series might be stuck in pu in perpetuity from the initial "When
people see the benefit of doing so" comment.

But if not, nevermind.

>> 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'.

Sure, all code's going to have problems, and the ab/i18n series is
around 1300 lines, so I'd be quite surprised if it didn't have some
bug.

> 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.

I was just wondering if there was anything particular that you were
worried about that could be addressed.

But as you've clarified there's nothing about it that I should be
explicitly addressing before it can move forward (if I've understood
you correctly).

Thanks for clarifying that and for your time.