[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87msixtqsy.fsf@trenco.lwn.net>
Date: Mon, 21 Oct 2024 09:32:29 -0600
From: Jonathan Corbet <corbet@....net>
To: Thorsten Blum <thorsten.blum@...ux.dev>
Cc: Thorsten Blum <thorsten.blum@...ux.dev>, workflows@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: Remove redundant word "for"
Thorsten Blum <thorsten.blum@...ux.dev> writes:
> s/for//
>
> Signed-off-by: Thorsten Blum <thorsten.blum@...ux.dev>
> ---
> Documentation/maintainer/pull-requests.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/maintainer/pull-requests.rst b/Documentation/maintainer/pull-requests.rst
> index 00b200facf67..0d63d9d7e347 100644
> --- a/Documentation/maintainer/pull-requests.rst
> +++ b/Documentation/maintainer/pull-requests.rst
> @@ -50,7 +50,7 @@ so outline what is contained here, why it should be merged, and what, if
> any, testing has been done. All of this information will end up in the tag
> itself, and then in the merge commit that the maintainer makes if/when they
> merge the pull request. So write it up well, as it will be in the kernel
> -tree for forever.
> +tree forever.
>
Applied, thanks.
jon
Powered by blists - more mailing lists