From: Martin Kepplinger <martink@posteo.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] samples: replace outdated permission statement with SPDX identifiers
Date: Sat, 18 Nov 2017 09:33:01 +0100 [thread overview]
Message-ID: <eee24bd5-4af5-5b13-0684-b637ed60ad97@posteo.de> (raw)
In-Reply-To: <20171117171300.69083b6b@lwn.net>
On 2017-11-18 01:13, Jonathan Corbet wrote:
> On Sat, 18 Nov 2017 00:43:46 +0100
> Martin Kepplinger <martink@posteo.de> wrote:
>
>> But Greg, people are listening to you. Please don't give advice in
>> directions that are not clearly correct for Linux. You know you could
>> have simply ack'd the initial mistake-fix in that case. It wouldn't have
>> hurt anybody.
>
> Sigh, it wasn't my intent to get Greg in trouble.
>
> Martin... please don't blame Greg here. What's going on (IMO) is that
> you've stumbled into something that we have just now begun to figure
> out. We very much *want* to rip out all that boilerplate, but we don't
> yet have a consensus on the proper way to do it. We haven't really even
> had the discussion yet. You've just had the poor luck to wander in at
> the wrong time and become part of that discussion.
>
> I'll confess that, when I saw your first patch, it crossed my mind to
> answer much like Greg did. But Greg always gets there first :)
>
Alright, noone is in trouble already I hope. Maybe I was a little harsh;
sorry Greg. I know less about law than about programming which might
have made me a little nervous here; In the end I want things to work for
Linux.
> The files that you are touching mostly have listed copyright holders in
> them. Should you feel like putting a bit more energy into this, one
> thing to do could be to copy them on a new posting of the patch and ask
> for acks. Assuming you get them, we should be able to clean up a bit of
> cruft in a way that's clearly supported by the copyright holders.
>
Makes sense. Thanks for clearing this up a bit! So as fixing your "own"
files is easier, I'll do that first :)
martin
next prev parent reply other threads:[~2017-11-18 8:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 9:50 [PATCH] samples: replace FSF address with web source in license notices Martin Kepplinger
2017-11-15 6:29 ` Greg KH
2017-11-15 7:46 ` Martin Kepplinger
2017-11-15 8:45 ` Greg KH
2017-11-15 20:44 ` [PATCH] samples: replace outdated permission statement with SPDX identifiers Martin Kepplinger
2017-11-16 11:41 ` Greg KH
2017-11-17 22:53 ` Jonathan Corbet
2017-11-17 23:43 ` Martin Kepplinger
2017-11-18 0:13 ` Jonathan Corbet
2017-11-18 8:33 ` Martin Kepplinger [this message]
2017-11-18 10:20 ` Greg KH
2017-11-18 10:17 ` Greg KH
2017-11-18 11:21 ` Martin Kepplinger
2017-11-16 13:56 ` Philippe Ombredanne
2017-11-22 22:23 ` [PATCH] samples: replace FSF address with web source in license notices Pavel Machek
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=eee24bd5-4af5-5b13-0684-b637ed60ad97@posteo.de \
--to=martink@posteo.de \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®