From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Diederik de Haas <didi.debian@cknow.org>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jonathan Corbet <corbet@lwn.net>,
"open list:EXT4 FILE SYSTEM" <linux-ext4@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: ext4: Fix full name of the GPL
Date: Mon, 23 Jan 2023 20:59:00 +0700 [thread overview]
Message-ID: <cb0187ce-7e40-c1e0-f2ce-fc1f9b45f5ad@gmail.com> (raw)
In-Reply-To: <3646506.8mSpapujdy@prancing-pony>
On 1/23/23 19:44, Diederik de Haas wrote:
> On Monday, 23 January 2023 03:10:58 CET Bagas Sanjaya wrote:
>> On Sun, Jan 22, 2023 at 07:05:51PM +0100, Diederik de Haas wrote:
>>> Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
>>
>> No patch description, really?
>
> Please disregard this patch.
> Next to 'style' issues, I now consider my initial view of the issue as a
> spelling error, incorrect. I would be changing the license and IANAL. I'm also
> not the copyright holder which I believe is needed to change the license.
>
> Apologies for the noise.
Nice to see you reply to the review.
However, as I noticed, it seems like your NAKed review replies
have the same wording, which make me wonder if these are written
by a bot behind your email handle. Next time, please write
variate your writings (write using different words but convey
the same meaning). I'm also sometimes hard to figure out
which words should I write.
Thanks.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-01-23 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 18:05 [PATCH] docs: ext4: Fix full name of the GPL Diederik de Haas
2023-01-23 2:10 ` Bagas Sanjaya
2023-01-23 12:44 ` Diederik de Haas
2023-01-23 13:59 ` 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=cb0187ce-7e40-c1e0-f2ce-fc1f9b45f5ad@gmail.com \
--to=bagasdotme@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=corbet@lwn.net \
--cc=didi.debian@cknow.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).