From: Diederik de Haas <didi.debian@cknow.org>
To: Jonathan Corbet <corbet@lwn.net>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH] docs: rv: Fix full name of the GPL
Date: Mon, 23 Jan 2023 15:22:54 +0100 [thread overview]
Message-ID: <2983169.1Ym2AYXvDY@prancing-pony> (raw)
In-Reply-To: <c9d6291f-8b50-bd37-f48c-d96834d990dd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On Monday, 23 January 2023 14:51:57 CET Bagas Sanjaya wrote:
> > Please disregard this patch.
> > I'm now sending a similar response as I'm sending to my other patch
> > submissions, which is the following:
> >
> > 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.
>
> Glad to reply, but I see your reply above as if it is written by
> a bot. Care to vary your sentences?
I already got a bounce as I am now considered a spammer :-/
So now I got to figure out how to fix this clusterfsck, without being seen as
a spammer/bot, while also trying to minimize the burden on others.
I couldn't agree more with (the first paragraph of)
https://lore.kernel.org/lkml/ad99d227-ce82-319b-6323-b70ac009d0e7@roeck-us.net/
and I therefor consider this a legal issue and not a spelling one.
I can't answer the legal issue, hence the request for retraction.
Regards,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-23 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 18:12 [PATCH] docs: rv: Fix full name of the GPL Diederik de Haas
2023-01-23 2:15 ` Bagas Sanjaya
2023-01-23 12:48 ` Diederik de Haas
2023-01-23 13:51 ` Bagas Sanjaya
2023-01-23 14:22 ` Diederik de Haas [this message]
2023-01-23 14:57 ` 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=2983169.1Ym2AYXvDY@prancing-pony \
--to=didi.debian@cknow.org \
--cc=bagasdotme@gmail.com \
--cc=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.