($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Quentin Schulz <foss+yocto@0leil.net>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	 docs@lists.yoctoproject.org
Cc: Quentin Schulz <foss+yocto@0leil.net>
Subject: [PATCH 0/3] new yocto-patches ML + some typo/syntax fixes
Date: Thu, 28 Mar 2024 16:07:13 +0100	[thread overview]
Message-ID: <20240328-yocto-patches-v1-0-1124fa0bc532@theobroma-systems.com> (raw)

Let's mention in the docs there's a new ML where to send patches.

While at it, fix some Python syntax issues and a URL typo.

Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
---
Quentin Schulz (3):
      conf.py: properly escape backslashes for latex_elements
      refer to new yocto-patches mailing list wherever appropriate
      contributor-guide: submit-changes: fix typo in URL

 documentation/conf.py                              | 4 ++--
 documentation/contributor-guide/submit-changes.rst | 4 ++--
 documentation/ref-manual/resources.rst             | 3 +++
 3 files changed, 7 insertions(+), 4 deletions(-)
---
base-commit: 29cee590d59294306600a119048a234f10375603
change-id: 20240328-yocto-patches-ca599f04dce0

Best regards,
-- 
Quentin Schulz <quentin.schulz@theobroma-systems.com>



             reply	other threads:[~2024-03-28 15:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 15:07 Quentin Schulz [this message]
2024-03-28 15:07 ` [PATCH 1/3] conf.py: properly escape backslashes for latex_elements Quentin Schulz
2024-03-29 11:12   ` [docs] " Michael Opdenacker
2024-03-29 11:16     ` Quentin Schulz
2024-03-28 15:07 ` [PATCH 2/3] refer to new yocto-patches mailing list wherever appropriate Quentin Schulz
2024-03-29 11:20   ` [docs] " Michael Opdenacker
2024-03-28 15:07 ` [PATCH 3/3] contributor-guide: submit-changes: fix typo in URL Quentin Schulz
2024-03-29 11:21   ` [docs] " Michael Opdenacker
2024-03-29 11:41     ` Quentin Schulz

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=20240328-yocto-patches-v1-0-1124fa0bc532@theobroma-systems.com \
    --to=foss+yocto@0leil.net \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@theobroma-systems.com \
    /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).