Re: [PATCH 0/9] i18n: add PO files to po/
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 4, 2011, 22:15 UTC
- Message-ID
- <7vaa9gbdyc.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CACBZZX5uz5cdoWebYOY-Omu0drnQasJB-12DMZyZ_NX17jzhmg@mail.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
Show 5 quoted lines
> I think it's a bit too premature to try to plan this all ahead, why > not just take patches to po/ and see what the friction points are, > then address those as they arise? > ... >> 3. how can we avoid this making "git log -p" output unusable?
These two are somewhat mutually exclusive. I _suspect_ that Jonathan might have been hinting me to eject everything under the current po/ directory, and bind that part of the tree as a submodule from another repository, which would give us "git log -p" cleanliness automatically. Taking more patches to po/ would not help that process, even though it won't hinder it.