From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
git@vger.kernel.org, "Ramkumar Ramachandra" <artagnon@gmail.com>,
"Peter Krefting" <peter@softwolves.pp.se>,
"Marcin Cieślak" <saper@saper.info>,
"Sam Reed" <sam@reedyboy.net>,
"Jan Engelhardt" <jengelh@medozas.de>, "Jan Krüger" <jk@jk.gs>,
"Nguyễn Thái Ngọc" <pclouds@gmail.com>
Subject: Re: [PATCH 0/9] i18n: add PO files to po/
Date: Tue, 04 Oct 2011 15:15:55 -0700 [thread overview]
Message-ID: <7vaa9gbdyc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACBZZX5uz5cdoWebYOY-Omu0drnQasJB-12DMZyZ_NX17jzhmg@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue, 4 Oct 2011 23:58:07 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> 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.
next prev parent reply other threads:[~2011-10-04 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 18:58 [PATCH 0/9] i18n: add PO files to po/ Ævar Arnfjörð Bjarmason
2011-10-03 18:58 ` [PATCH 1/9] po/is.po: add Icelandic translation Ævar Arnfjörð Bjarmason
2011-10-03 18:58 ` [PATCH 3/9] po/de.po: update German translation Ævar Arnfjörð Bjarmason
2011-10-03 18:58 ` [PATCH 4/9] po/en_GB.po: add British English translation Ævar Arnfjörð Bjarmason
2011-10-03 18:58 ` [PATCH 5/9] po/pl.po: add Polish translation Ævar Arnfjörð Bjarmason
2011-10-03 18:58 ` [PATCH 6/9] po/sv.po: add Swedish translation Ævar Arnfjörð Bjarmason
2011-10-03 18:58 ` [PATCH 7/9] po/hi.po: add Hindi Translation Ævar Arnfjörð Bjarmason
2011-10-04 4:55 ` Ramkumar Ramachandra
2011-10-03 18:58 ` [PATCH 8/9] po/hi.po: Eliminate fuzzy translations Ævar Arnfjörð Bjarmason
2011-10-03 22:06 ` [PATCH 0/9] i18n: add PO files to po/ Jonathan Nieder
2011-10-03 22:53 ` Nguyen Thai Ngoc Duy
2011-10-04 21:58 ` Ævar Arnfjörð Bjarmason
2011-10-04 22:15 ` Junio C Hamano [this message]
2011-10-05 3:16 ` Jonathan Nieder
2011-10-05 4:09 ` Ramkumar Ramachandra
2011-10-06 9:29 ` Peter Krefting
2011-10-11 7:58 ` Peter Krefting
2011-10-05 13:44 ` Peter Krefting
2011-10-04 22:09 ` Nguyen Thai Ngoc Duy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vaa9gbdyc.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
--cc=jk@jk.gs \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=peter@softwolves.pp.se \
--cc=sam@reedyboy.net \
--cc=saper@saper.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.