From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Oliver Neukum <oneukum@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
Finn Thain <fthain@linux-m68k.org>
Cc: Linux SCSI <linux-scsi@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kernel Janitors <kernel-janitors@vger.kernel.org>,
Ali Akcaagac <aliakc@web.de>, Jamie Lenehan <lenehan@twibble.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 3/3] Documentation: scsi: dc395x: Remove reference to 2.4 driver
Date: Wed, 10 May 2023 15:57:51 +0700 [thread overview]
Message-ID: <7e3e90f2-49bd-46f6-ce1e-bd3263e6eb32@gmail.com> (raw)
In-Reply-To: <8536273d-20a4-1993-1381-b50e44701835@suse.com>
On 5/9/23 15:55, Oliver Neukum wrote:
> Hi,
>
> the documentation of a kernel should document that kernel.
>
> Now, we have a perfectly fine tool named "git" which allows
> for metadocumentation. May I suggest that you respin the patch
> and include a link to the old stuff, which somebody has been
> nice enough to find, in the change log?
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-05-10 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:27 [PATCH 0/3] dc395x stale reference cleanup Bagas Sanjaya
2023-05-05 8:27 ` [PATCH 1/3] MAINTAINERS: Drop DC395x list and site Bagas Sanjaya
2023-05-05 9:16 ` Dan Carpenter
2023-05-06 2:21 ` Bagas Sanjaya
2023-05-06 21:01 ` Ali Akcaagac
2023-05-05 8:27 ` [PATCH 2/3] Documentation: scsi: dc395x: Replace non-functional twibble.org list Bagas Sanjaya
2023-05-05 8:27 ` [PATCH 3/3] Documentation: scsi: dc395x: Remove reference to 2.4 driver Bagas Sanjaya
2023-05-05 10:12 ` Finn Thain
2023-05-05 13:34 ` Jonathan Corbet
2023-05-06 0:17 ` Finn Thain
2023-05-09 8:55 ` Oliver Neukum
2023-05-10 8:57 ` Bagas Sanjaya [this message]
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=7e3e90f2-49bd-46f6-ce1e-bd3263e6eb32@gmail.com \
--to=bagasdotme@gmail.com \
--cc=aliakc@web.de \
--cc=corbet@lwn.net \
--cc=fthain@linux-m68k.org \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lenehan@twibble.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oneukum@suse.com \
/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