From: Jonathan Corbet <corbet@lwn.net>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>, jesper.juhl@gmail.com
Subject: Re: [PATCH] Documentation: Process: Add a note about git way of applying patch
Date: Thu, 07 Sep 2023 06:48:11 -0600 [thread overview]
Message-ID: <87bkee40ac.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230907115420.28642-1-unixbhaskar@gmail.com>
Bhaskar Chowdhury <unixbhaskar@gmail.com> writes:
> cc: jesper.juhl@gmail.com
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.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
next prev parent reply other threads:[~2023-09-07 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 11:52 Bhaskar Chowdhury
2023-09-07 12:48 ` Jonathan Corbet [this message]
2023-09-07 12:58 ` Bhaskar Chowdhury
2023-09-07 13:25 ` Jonathan Corbet
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=87bkee40ac.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=jesper.juhl@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=unixbhaskar@gmail.com \
--cc=workflows@vger.kernel.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