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

Re: [PATCH] README.md: add CodingGuidelines and a link for Translators

From
Philip Oakley <philipoakley@iee.email>
Date
Jan 15, 2022, 00:08 UTC
Message-ID
<6b626f9d-05d6-1903-0b38-e3566e357472@iee.email>
In-Reply-To
<xmqq7db2avij.fsf@gitster.g>
On 14/01/2022 20:54, Junio C Hamano wrote:
Show 6 quoted lines
> "Philip Oakley via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> From: Philip Oakley <philipoakley@iee.email>
>>
>> Also space out the list joining instructions and clarify the subscription
> the instructions to join the list?
Correct.
Show 6 quoted lines
>
>>  requests, comments and patches to git@vger.kernel.org (read
>> -[Documentation/SubmittingPatches][] for instructions on patch submission).
>> +[Documentation/SubmittingPatches][] for instructions on patch submission
>> +and [Documentation/CodingGuidelines]() ).
> Remind me the significance of using [] and () after [File Reference]?
The [] is the original method used by the unchanged text, while the ()
appears to be the method required now.
 
Show 12 quoted lines
>
>> +Those wishing to help with error message translation (localization L10)
>> +should see [po/README.md]()
> Same here.
>
> https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links
>
> seems to indicate () is to enclose URL the text goes to, and if
> there is no URL to go to, perhaps it does the right thing, but the
> current page (which has "[Documentation/SubmittingPatches][]" and
> all other reference into in-tree files with that format) seems to
> render correctly with links that work, so...

Unfortunately it `[]` is not working for me for the new additions. GitHub magic?

Show 13 quoted lines
>
>> +(a `po` file is a portable object file for the translations).
>> +
>>  To subscribe to the list, send an email with just "subscribe git" in
>> -the body to majordomo@vger.kernel.org. The mailing list archives are
>> -available at <https://lore.kernel.org/git/>,
>> +the body to majordomo@vger.kernel.org (not the list). The mailing list
>> +archives are available at <https://lore.kernel.org/git/>,
>>  <http://marc.info/?l=git> and other archival sites.
>>  
>>  Issues which are security relevant should be disclosed privately to
>>
>> base-commit: 1ffcbaa1a5f10c9f706314d77f88de20a4a498c2
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 11 in “README.md: add CodingGuidelines and a link for Translators”
  1. README.md: add CodingGuidelines and a link for TranslatorsPhilip Oakley via GitGitGadget, Jan 14, 2022
  2. Junio C HamanoJan 14, 2022
  3. Philip OakleyJan 15, 2022
  4. Junio C HamanoJan 15, 2022
  5. README.md: add CodingGuidelines and a link for TranslatorsPhilip Oakley via GitGitGadget, Jan 16, 2022
  6. Junio C HamanoJan 16, 2022
  7. Philip OakleyJan 17, 2022
  8. Bagas SanjayaJan 17, 2022
  9. Philip OakleyJan 17, 2022
  10. Junio C HamanoJan 17, 2022
  11. README.md: add CodingGuidelines and a link for TranslatorsPhilip Oakley via GitGitGadget, Jan 17, 2022

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.