From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: baruch@tkos.co.il, docs@lists.yoctoproject.org
Cc: michael.opdenacker@bootlin.com
Subject: Re: [docs] [PATCH] contributor-guide: fix lore URL
Date: Mon, 5 Feb 2024 12:17:07 +0100 [thread overview]
Message-ID: <8ece52f8-904b-414e-ac2c-a0f05f827e41@bootlin.com> (raw)
In-Reply-To: <7542f40a18bc1485daaf503d1ab05019be088142.1707119145.git.baruch@tkos.co.il>
Hi Baruch
On 2/5/24 at 08:45, baruch@tkos.co.il via lists.yoctoproject.org wrote:
> Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> documentation/contributor-guide/submit-changes.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/documentation/contributor-guide/submit-changes.rst b/documentation/contributor-guide/submit-changes.rst
> index 95728c25c615..61f3157d602e 100644
> --- a/documentation/contributor-guide/submit-changes.rst
> +++ b/documentation/contributor-guide/submit-changes.rst
> @@ -438,7 +438,7 @@ their e-mail clients will default to including your email address in the
> conversation anyway.
>
> Anyway, you'll also be able to access the new messages on mailing list archives,
> -either through a web browser, or for the lists archived on https://lore.kernelorg,
> +either through a web browser, or for the lists archived on https://lore.kernel.org,
> through an individual newsgroup feed or a git repository.
Oops, good catch, thanks a lot!
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Merged into "master-next"
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-02-05 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 7:45 [PATCH] contributor-guide: fix lore URL Baruch Siach
2024-02-05 11:17 ` Michael Opdenacker [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ece52f8-904b-414e-ac2c-a0f05f827e41@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=baruch@tkos.co.il \
--cc=docs@lists.yoctoproject.org \
/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.
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).