[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bkee40ac.fsf@meer.lwn.net>
Date: Thu, 07 Sep 2023 06:48:11 -0600
From: Jonathan Corbet <corbet@....net>
To: Bhaskar Chowdhury <unixbhaskar@...il.com>,
workflows@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Bhaskar Chowdhury <unixbhaskar@...il.com>, jesper.juhl@...il.com
Subject: Re: [PATCH] Documentation: Process: Add a note about git way of
applying patch
Bhaskar Chowdhury <unixbhaskar@...il.com> writes:
> cc: jesper.juhl@...il.com
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
> ---
> Documentation/process/applying-patches.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/process/applying-patches.rst b/Documentation/process/applying-patches.rst
> index c269f5e1a0a3..201b9900bffe 100644
> --- a/Documentation/process/applying-patches.rst
> +++ b/Documentation/process/applying-patches.rst
> @@ -6,6 +6,13 @@ Applying Patches To The Linux Kernel
> Original by:
> Jesper Juhl, August 2005
>
> +
> +.. applying patch by Git::
> +
> + You can use the below syntax to patch in git repository
> + git-apply --whitespace=error-all <patchfile>
> +
> +
> .. note::
>
> This document is obsolete. In most cases, rather than using ``patch``
So why are you sending a patch ... with no changelog ... adding a
useless label ... and Sphinx syntax errors ... to a document that is
explicitly marked as being obsolete?
jon
Powered by blists - more mailing lists