public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
	Joshua Watt <JPEWhacker@gmail.com>
Subject: [PATCH 1/5] contributor guide: call section "Reporting a defect"
Date: Fri, 11 Aug 2023 19:55:23 +0200	[thread overview]
Message-ID: <20230811175527.1116864-2-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230811175527.1116864-1-michael.opdenacker@bootlin.com>

From: Michael Opdenacker <michael.opdenacker@bootlin.com>

Instead of "Submitting a defect".

We all write bugs, and nobody needs documentation
support for doing so!

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Joshua Watt <JPEWhacker@gmail.com>
---
 documentation/contributor-guide/index.rst                       | 2 +-
 .../contributor-guide/{submit-defect.rst => report-defect.rst}  | 2 +-
 documentation/dev-manual/debugging.rst                          | 2 +-
 documentation/ref-manual/resources.rst                          | 2 +-
 documentation/ref-manual/system-requirements.rst                | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)
 rename documentation/contributor-guide/{submit-defect.rst => report-defect.rst} (98%)

diff --git a/documentation/contributor-guide/index.rst b/documentation/contributor-guide/index.rst
index 7a39f994e2..8fa65045a3 100644
--- a/documentation/contributor-guide/index.rst
+++ b/documentation/contributor-guide/index.rst
@@ -19,7 +19,7 @@ this.
    :numbered:
 
    identify-component
-   submit-defect
+   report-defect
    recipe-style-guide
    submit-change
 
diff --git a/documentation/contributor-guide/submit-defect.rst b/documentation/contributor-guide/report-defect.rst
similarity index 98%
rename from documentation/contributor-guide/submit-defect.rst
rename to documentation/contributor-guide/report-defect.rst
index 527ffb2dc0..8ef133b842 100644
--- a/documentation/contributor-guide/submit-defect.rst
+++ b/documentation/contributor-guide/report-defect.rst
@@ -1,6 +1,6 @@
 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
 
-Submitting a Defect Against the Yocto Project and OpenEmbedded
+Reporting a Defect Against the Yocto Project and OpenEmbedded
 **************************************************************
 
 You can use the Yocto Project instance of
diff --git a/documentation/dev-manual/debugging.rst b/documentation/dev-manual/debugging.rst
index 3a8d5080ce..890578cc05 100644
--- a/documentation/dev-manual/debugging.rst
+++ b/documentation/dev-manual/debugging.rst
@@ -1235,7 +1235,7 @@ Here are some other tips that you might find useful:
    :yocto_bugs:`Bugzilla <>`. For information on
    how to submit a bug against the Yocto Project, see the Yocto Project
    Bugzilla :yocto_wiki:`wiki page </Bugzilla_Configuration_and_Bug_Tracking>`
-   and the ":doc:`../contributor-guide/submit-defect`" section.
+   and the ":doc:`../contributor-guide/report-defect`" section.
 
    .. note::
 
diff --git a/documentation/ref-manual/resources.rst b/documentation/ref-manual/resources.rst
index 324d1fad10..8c3726e83b 100644
--- a/documentation/ref-manual/resources.rst
+++ b/documentation/ref-manual/resources.rst
@@ -45,7 +45,7 @@ your expectations).
 For a general procedure and guidelines on how to use Bugzilla to submit a bug
 against the Yocto Project, see the following:
 
--  The ":doc:`../contributor-guide/submit-defect`"
+-  The ":doc:`../contributor-guide/report-defect`"
    section in the Yocto Project and OpenEmbedded Contributor Guide.
 
 -  The Yocto Project :yocto_wiki:`Bugzilla wiki page </Bugzilla_Configuration_and_Bug_Tracking>`
diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst
index 9ae7b4e63b..66ab65d2b7 100644
--- a/documentation/ref-manual/system-requirements.rst
+++ b/documentation/ref-manual/system-requirements.rst
@@ -134,7 +134,7 @@ tested by the &DISTRO; release ("&DISTRO_NAME;"), but no longer are:
       interested in hearing about your experience. For information on
       how to submit a bug, see the Yocto Project
       :yocto_wiki:`Bugzilla wiki page </Bugzilla_Configuration_and_Bug_Tracking>`
-      and the ":doc:`../contributor-guide/submit-defect`"
+      and the ":doc:`../contributor-guide/report-defect`"
       section in the Yocto Project and OpenEmbedded Contributor Guide.
 
 Required Packages for the Build Host
-- 
2.34.1



  reply	other threads:[~2023-08-11 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 17:55 [PATCH 0/5] Contributor Guide updates michael.opdenacker
2023-08-11 17:55 ` michael.opdenacker [this message]
2023-08-11 17:55 ` [PATCH 2/5] contributor-guide: remove obsolete pkg-config guidelines michael.opdenacker
2023-08-11 17:55 ` [PATCH 3/5] contributor guide: remove unnecessary information about mailing lists michael.opdenacker
2023-08-11 17:55 ` [PATCH 4/5] contributor-guide: clarification about patchtest michael.opdenacker
2023-08-11 17:55 ` [PATCH 5/5] contributor guide: update instructions for making and sharing changes michael.opdenacker

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=20230811175527.1116864-2-michael.opdenacker@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=JPEWhacker@gmail.com \
    --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