U-boot Archive mirror
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [v3 1/2] doc: process.rst: Use subsubheading for "Phases of the Development Process"
Date: Tue, 21 May 2024 11:23:01 +0200	[thread overview]
Message-ID: <b160b75b-513a-44e1-ab1c-cdcb42a44dda@cherry.de> (raw)
In-Reply-To: <20240517174930.1028063-1-trini@konsulko.com>

Hi Tom,

On 5/17/24 7:49 PM, Tom Rini wrote:
> These sections which talk about the different phases of the development
> process should be using the subsubheading identifier.
> 
> Signed-off-by: Tom Rini <trini@konsulko.com>
> ---
> Changes in v3:
> None
> 
> Changes in v2:
> None
> 
> Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
>   doc/develop/process.rst | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/doc/develop/process.rst b/doc/develop/process.rst
> index 92477d05dd85..a66540a698c1 100644
> --- a/doc/develop/process.rst
> +++ b/doc/develop/process.rst
> @@ -34,7 +34,7 @@ It is followed by a *Stabilization Period*.
>   The end of a Release Cycle is marked by the release of a new U-Boot version.
>   
>   Merge Window
> -------------
> +^^^^^^^^^^^^
>   
>   The Merge Window is the period when new patches get submitted (and hopefully
>   accepted) for inclusion into U-Boot mainline. This period lasts for 21 days (3
> @@ -44,7 +44,7 @@ This is the only time when new code (like support for new processors or new
>   boards, or other new features or reorganization of code) is accepted.
>   
>   Twilight Time
> --------------
> +^^^^^^^^^^^^^
>   
>   Usually patches do not get accepted as they are - the peer review that takes
>   place will usually require changes and resubmissions of the patches before they
> @@ -65,13 +65,13 @@ the Merge Window does not preclude patches that were already posted from being
>   merged for the upcoming release.
>   
>   Stabilization Period
> ---------------------
> +^^^^^^^^^^^^^^^^^^^^
>   
>   During the Stabilization Period only patches containing bug fixes get
>   applied.
>   
>   Corner Cases
> -------------
> +^^^^^^^^^^^^
>   
>   Sometimes it is not clear if a patch contains a bug fix or not.
>   For example, changes that remove dead code, unused macros etc. or

Wondering if we shouldn't put:

Differences to the Linux Development Process

section under the "Phases of the development process" section as well?

Otherwise,

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

  parent reply	other threads:[~2024-05-21  9:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 17:49 [v3 1/2] doc: process.rst: Use subsubheading for "Phases of the Development Process" Tom Rini
2024-05-17 17:49 ` [v3 2/2] doc: process.rst: Document device tree resync rules Tom Rini
2024-05-21  9:27   ` Quentin Schulz
2024-05-21 16:38     ` Tom Rini
2024-05-21  9:23 ` Quentin Schulz [this message]
2024-05-21 16:36   ` [v3 1/2] doc: process.rst: Use subsubheading for "Phases of the Development Process" Tom Rini

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=b160b75b-513a-44e1-ab1c-cdcb42a44dda@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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).