From: Martin Kepplinger <martink@posteo.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: catalin.marinas@arm.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: replace FSF address with web source in license notices
Date: Tue, 14 Nov 2017 11:21:49 +0100 [thread overview]
Message-ID: <969a24d542fbd98ec8badf64e9d1909c@posteo.de> (raw)
In-Reply-To: <20171114100202.bbegvtz6jckuyzcm@dhcp22.suse.cz>
Am 14.11.2017 11:02 schrieb Michal Hocko:
> On Tue 14-11-17 10:55:35, Martin Kepplinger wrote:
>> Am 14.11.2017 10:49 schrieb Michal Hocko:
>> > On Tue 14-11-17 10:44:38, Martin Kepplinger wrote:
>> > > A few years ago the FSF moved and "59 Temple Place" is wrong. Having
>> > > this
>> > > still in our source files feels old and unmaintained.
>> > >
>> > > Let's take the license statement serious and not confuse users.
>> > >
>> > > As https://www.gnu.org/licenses/gpl-howto.html suggests, we replace
>> > > the
>> > > postal address with "<http://www.gnu.org/licenses/>" in the mm
>> > > directory.
>> >
>> > Why to change this now? Isn't there a general plan to move to SPDX?
>>
>> Shouldn't a move to SPDX only be additions to what we currently have?
>> That's
>> at least what the "reuse" project suggests, see
>> https://reuse.software/practices/
>> with "Don’t remove existing headers, but only add to them."
>
> I thought the primary motivation was to unify _all_ headers and get rid
> of all the duplication. (aside from files which do not have any license
> which is under discussion elsewhere).
I doubt that this can be fully accieved in the long run :) It'd be nice
of course in
some way.
But I also doubt that it'd be so easy to remove the permission
statements.
The FSF who's license we use suggest to have them, but others do too.
And as mentioned, "using SPDX" doesn't imply "not having permission
statements".
But I think that's off-topic actually. Moving to SPDX could still be
done in
any way whatsoever after this. This change fixes a *mistake* and can
reduce
confusion or even support license compliance, who knows :)
thanks
martin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-14 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 9:44 Martin Kepplinger
2017-11-14 9:49 ` Michal Hocko
2017-11-14 9:55 ` Martin Kepplinger
2017-11-14 10:02 ` Michal Hocko
2017-11-14 10:21 ` Martin Kepplinger [this message]
2017-11-22 22:20 ` 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=969a24d542fbd98ec8badf64e9d1909c@posteo.de \
--to=martink@posteo.de \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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