git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Philip Oakley <philipoakley@iee.email>
Subject: Re: [PATCH] README.md: add CodingGuidelines and a link for Translators
Date: Fri, 14 Jan 2022 12:54:12 -0800	[thread overview]
Message-ID: <xmqq7db2avij.fsf@gitster.g> (raw)
In-Reply-To: <pull.1115.git.1642182615339.gitgitgadget@gmail.com> (Philip Oakley via GitGitGadget's message of "Fri, 14 Jan 2022 17:50:15 +0000")

"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?

>  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]?

> +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...

> +(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

  reply	other threads:[~2022-01-14 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 17:50 [PATCH] README.md: add CodingGuidelines and a link for Translators Philip Oakley via GitGitGadget
2022-01-14 20:54 ` Junio C Hamano [this message]
2022-01-15  0:08   ` Philip Oakley
2022-01-15  0:47     ` Junio C Hamano
2022-01-16 16:11 ` [PATCH v2] " Philip Oakley via GitGitGadget
2022-01-16 22:47   ` Junio C Hamano
2022-01-17 18:08     ` Philip Oakley
2022-01-17  9:00   ` Bagas Sanjaya
2022-01-17 17:52     ` Philip Oakley
2022-01-17 18:49     ` Junio C Hamano
2022-01-17 18:18   ` [PATCH v3] " Philip Oakley via GitGitGadget

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq7db2avij.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=philipoakley@iee.email \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).