git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 0/1] handling mistranslation reports

From
Philip Oakley <philipoakley@iee.org>
Date
Aug 16, 2015, 18:54 UTC
Message-ID
<134837D8A3EE41ECBE65D228CC57818B@PhilipOakley>
In-Reply-To
<CANYiYbEKoF6GhezPmR1fGxRqTvZAE4L2xguvvwFEWqWBkOp9tw@mail.gmail.com>
From: "Jiang Xin" <worldhello.net@gmail.com>
Show 46 quoted lines
> 2015-08-04 6:29 GMT+08:00 Philip Oakley <philipoakley@iee.org>:
>> 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.
Yes 0/1 was the cover letter and 1/1 was the actual patch.

I have not found a way of sending, via my 'git send-email' (*), a single patch with its integrated cover-letter at the beginning. I can easily add short notes after a 3-dashes in the commit, but it is not the same as a cover-letter ...

Hopefully, you got the 1/1. Unfortunately, the Git list is rejecting my patches (and just my patches), as sent via send-email, and at the moment I have no way of debugging and diagnosing that issue.

Show 7 quoted lines
>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.
Thanks. Will review.
>
> -- 
> Jiang Xin
> --
(*) https://groups.google.com/forum/#!topic/msysgit/U85cSXd-Uv0 
Previous: Philip Oakley
Message 4 of 4 in “Re: [PATCH v2 0/1] handling mistranslation reports”
  1. Jiang XinAug 16, 2015
  2. po/README: Update directions for l10n contributorsJiang Xin, Aug 16, 2015
  3. Philip OakleyAug 16, 2015
  4. Philip OakleyAug 16, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.