lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4678664.8dpOeDNDtA@ripper>
Date:   Fri, 05 Feb 2021 08:47:38 +0100
From:   Sven Eckelmann <sven@...fation.org>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Simon Wunderlich <sw@...onwunderlich.de>, davem@...emloft.net,
        netdev@...r.kernel.org, b.a.t.m.a.n@...ts.open-mesh.org
Subject: Re: [PATCH 2/4] batman-adv: Update copyright years for 2021

On Thursday, 4 February 2021 20:58:36 CET Jakub Kicinski wrote:
> Back when I was working for a vendor I had a script which used git to
> find files touched in current year and then a bit of sed to update the
> dates. Instead of running your current script every Jan, you can run
> that one every Dec.

Just as an additional anecdote: Just had the situation that a vendor 
complained that the user visible copyright notice was still 2020 for a project 
published in 2021 but developed and tested 2020 (and thus tagged + packaged in 
2020).

Now to something more relevant: what do you think about dropping the copyright 
year [1]?

Kind regards,
	Sven

[1] https://reuse.software/faq/#years-copyright


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ