[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aMqLXk-VyIKR3PtH@archie.me>
Date: Wed, 17 Sep 2025 17:20:14 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Thorsten Blum <thorsten.blum@...ux.dev>,
Jonathan Corbet <corbet@....net>
Cc: Randy Dunlap <rdunlap@...radead.org>, workflows@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] docs: maintainer: Fix ambiguous subheading formatting
On Wed, Sep 17, 2025 at 12:29:44AM +0200, Thorsten Blum wrote:
> diff --git a/Documentation/maintainer/maintainer-entry-profile.rst b/Documentation/maintainer/maintainer-entry-profile.rst
> index cda5d691e967..d36dd892a78a 100644
> --- a/Documentation/maintainer/maintainer-entry-profile.rst
> +++ b/Documentation/maintainer/maintainer-entry-profile.rst
> @@ -59,6 +59,7 @@ week) that patches might be considered for merging and when patches need to
> wait for the next -rc. At a minimum:
>
> - Last -rc for new feature submissions:
> +
> New feature submissions targeting the next merge window should have
> their first posting for consideration before this point. Patches that
> are submitted after this point should be clear that they are targeting
> @@ -68,6 +69,7 @@ wait for the next -rc. At a minimum:
> submissions should appear before -rc5.
>
> - Last -rc to merge features: Deadline for merge decisions
> +
> Indicate to contributors the point at which an as yet un-applied patch
> set will need to wait for the NEXT+1 merge window. Of course there is no
> obligation to ever accept any given patchset, but if the review has not
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@...il.com>
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists