netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Simon Wunderlich <sw@simonwunderlich.de>,
	Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH 2/4] batman-adv: Update copyright years for 2021
Date: Thu, 04 Feb 2021 08:54:33 +0100	[thread overview]
Message-ID: <3636307.aAJz7UTs6F@ripper> (raw)
In-Reply-To: <20210203163506.4b4dbff0@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On Thursday, 4 February 2021 01:35:06 CET Jakub Kicinski wrote:
[...]
> Is this how copyright works? I'm not a layer, but I thought it was
> supposed to reflect changes done to given file in a given year.

<irony>Because we all know that the first thing a person is doing when 
submitting a change is to update the copyright year.</irony>

So we have either the option to:

* not update it at all (as in many kernel sources)
* don't have it listed explicitly (as seen in other kernel sources)
* update it once a year

I personally like to have a simple solution so I don't have to deal with this 
kind of details while doing interesting things. The current "solution"
was to handle the copyright notices year for the whole project as one entity - 
once per year and then ignore it for the rest of the year.

And I would also prefer not to start a discussion about the differences 
between the inalienable German Urheberrecht, pre 1989 anglo-american 
copyright, post 1989 anglo american copyright and other copyright like laws.

Kind regards,
	Sven


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-02-04  7:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 17:40 [PATCH 0/4] pull request for net-next: batman-adv 2021-02-02 Simon Wunderlich
2021-02-02 17:40 ` [PATCH 1/4] batman-adv: Start new development cycle Simon Wunderlich
2021-02-04  0:33   ` Jakub Kicinski
2021-02-04  7:41     ` Sven Eckelmann
2021-02-02 17:40 ` [PATCH 2/4] batman-adv: Update copyright years for 2021 Simon Wunderlich
2021-02-04  0:35   ` Jakub Kicinski
2021-02-04  0:37     ` Randy Dunlap
2021-02-04  7:54     ` Sven Eckelmann [this message]
2021-02-04 19:58       ` Jakub Kicinski
2021-02-05  7:47         ` Sven Eckelmann
2021-02-05 19:37           ` Jakub Kicinski
2021-02-02 17:40 ` [PATCH 3/4] batman-adv: Avoid sizeof on flexible structure Simon Wunderlich
2021-02-02 17:40 ` [PATCH 4/4] batman-adv: Fix names for kernel-doc blocks Simon Wunderlich

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=3636307.aAJz7UTs6F@ripper \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sw@simonwunderlich.de \
    /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).