Jiang Xin <worldhello.net@xxxxxxxxx> writes: > 2012/2/2 Junio C Hamano <gitster@xxxxxxxxx>: > ... >> (6) From time to time, the l10n coordinator will pull from "git.git" when >> meaningful number of changes are made to the translatable strings. I >> hope this would happen much less often than once per week, preferably >> much less frequently. The l10n coordinator updates po/git.pot and >> makes a commit, and notifies the l10n teams. > > notifies the l10n teams using another mailing list maybe. I personally think using the regular git@xxxxxxxxxxxxxxx list would be preferrable for this. People who translate would want to learn the reasoning that led to the final phrasing of the messages to come up with usable translation, and following the main list would be one way to do so. Having to follow two separate list will be an unnecessary burden. But the choice of how to coordinate his or her work with the l10n teams is entirely up to the l10n coordinator. >> And i18n patches that modify the _() markings in the source code, will >> only go through "git.git" tree in the normal channel, IOW, this mailing >> list. > > Yeah, works on the codes but not the po files still send to this list. Many if not all of the po files in gitk and git-gui were discussed on this list and integrated to the tree with the usual "format-patch to am" review flow just fine. You keep saying that l10n patches does not work, but that is patently wrong. It is a different matter if it is the most convenient for l10n patches for both the l10n folks and others to review and discuss on this list, or on web based services like GitHub. -- 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