{"thread":{"id":"34994","subject":"[L10N] Proposed updates of po/git.pot in pu branch","startedAt":"2013-09-22T17:00:14Z","lastAt":"2013-09-22T17:00:14Z","messageCount":1,"participants":["Jiang Xin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"228033","messageId":"CANYiYbHDKVxtSpVnQq8nGMgnJVYPZcs1-tdgi+kku0upCgSguA@mail.gmail.com","threadId":"34994","inReplyTo":null,"subject":"[L10N] Proposed updates of po/git.pot in pu branch","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2013-09-22T17:00:14Z","receivedAt":"2013-09-22T17:00:14Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"Hi, Git l10n teams\n\nI created a new branch \"pu\" in the l10 coordinator repository to\nhold proposed updates of \"po/git.pot\" for translations. See commit\nlog for hints:\n\ncommit e9d227174abf2b7f66a7027a509886f9cba1adea\n\n    l10n: git.pot: proposed updates since v1.8.4 (48+)\n\n    The 1st round of Git l10n often starts very late duing the release\n    cycle of Git, usually after the release of rc1. This leads to a\n    gaint update of \"po/git.pot\" and lots of works for translators with\n    a tight deadline (about one week).\n\n    This \"pu\" branch holds proposed updates of the file \"po/git.pot\" for\n    Git next release (1.8.5), and will be updated and rewound without\n    notification when there are remarkable updates for it.\n\n    Translators could work on this \"pu\" branch before the l10n coordinator\n    starts the 1st round of l10n for this release cycle of Git, and\n    rebase their works onto the master branch (with the commit for the\n    1st round of l10n), then send pull request to the l10n coordinator.\n\n    Please note:\n\n     1. Because this branch will be rewound occasionally, translators\n        SHOULD NOT merge, but SHOULD rebase to this rewound branch\n        instead.\n\n            $ git fetch git://github.com/git-l10n/git-po.git pu\n            $ git rebase --onto FETCH_HEAD HEAD~1\n\n     2. Update your translated message file \"po/XX.po\".\n\n            $ msgmerge --add-location --backup=off -U \"po/XX.po\" \\\n              po/git.pot\n\n     3. Then start to translate \"po/XX.po\" and commit.\n\n     4. DO NOT send pull request to the l10n coordinator for\n        translations on this \"pu\" branch.\n\n     5. When the l10n coordinator starts the 1st round l10n for the\n        current Git release cycle, translators should rebase and squash\n        their works onto the master branch, and then send pull request.\n\n            $ git fetch git://github.com/git-l10n/git-po.git master\n            $ git rebase --onto FETCH_HEAD HEAD~1\n\n    Signed-off-by: Jiang Xin <worldhello.net@gmail.com>\n\nHope this may help, and not bring troubles.\n\n-- \nJiang Xin\n"}]}