From: Jiang Xin Date: Sun, 16 Aug 2015 05:46:07 GMT Subject: Re: [PATCH v2 0/1] handling mistranslation reports Message-ID: In-Reply-To: <1438640973-1452-1-git-send-email-philipoakley@iee.org> 2015-08-04 6:29 GMT+08:00 Philip Oakley : > Hi Jiang, > > This is my updated patch based on your feedback at $gmane/275141 > and $gmane/275142. > > I've used most of your wording, though have retained a comment on > considering if the translation could be held here. > > My original commentary is below, along with the inter-diff between versions. > > - > Recently, on the 'Git for human beings' list, a user reported a > mistranslation and asked if/what could be done, with a suggested > alternate text [1]. > > I pointed the user at the po/README for general guidance. > Unfortunately the user was noting a Spanish (es) translation error which > is not held in your tree, but the README does include how to start a new > translation. This led to a misunderstanding with regard to which aspect > of the README was being referred to (private discussion with Junio). > > This patch separates out the three different aspects that caused confusion > and explicitly brings out what to do for translations not currently held here. > > I hope my suggested patch will fit with your approach and ask for comments > (or Ack / Nack). > > regards > > Philip > > [1] https://groups.google.com/forum/#!topic/git-users/rK5oU6k8Tzw > > Interdiff: The subject is "[PATCH v2 0/1]" and I wonder where is the real patch file ("v2 1/1") aside of this cover letter. But today I have time to read it carefully, and I know this is a fixup commit. I squash this reroll to last commit for this series, and simplify both the commit and the commit log. See patch v3 in the next email. -- Jiang Xin