Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> 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. -- 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