[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: stop doing "grand replace" updates to copyright years
From: |
Jean Abou Samra |
Subject: |
Re: RFC: stop doing "grand replace" updates to copyright years |
Date: |
Wed, 15 Feb 2023 17:45:37 +0100 |
User-agent: |
Evolution 3.46.3 (3.46.3-1.fc37) |
Le lundi 13 février 2023 à 23:50 +0100, Han-Wen Nienhuys a écrit :
> it is weird, but so is doing the grand update. We could decide to trim
> our license headers to a smaller SPDX identifier without a year, but
> we still have another year to go before a decision would make a
> difference.
I prefer not postponing decisions.
My preferred route is to just remove those copyright headers or
at least the years; they have little significance legally anyway (as
David explained).
signature.asc
Description: This is a digitally signed message part
- Re: RFC: stop doing "grand replace" updates to copyright years, (continued)
- Re: RFC: stop doing "grand replace" updates to copyright years, Luca Fascione, 2023/02/15
- Re: RFC: stop doing "grand replace" updates to copyright years, Jean Abou Samra, 2023/02/15
- Re: RFC: stop doing "grand replace" updates to copyright years, Wol, 2023/02/14
- Re: RFC: stop doing "grand replace" updates to copyright years, David Kastrup, 2023/02/14
- Re: RFC: stop doing "grand replace" updates to copyright years, Wols Lists, 2023/02/15
- Re: RFC: stop doing "grand replace" updates to copyright years, David Kastrup, 2023/02/15
- Re: RFC: stop doing "grand replace" updates to copyright years, Wol, 2023/02/15
- Re: RFC: stop doing "grand replace" updates to copyright years, David Kastrup, 2023/02/15
- Re: RFC: stop doing "grand replace" updates to copyright years,
Jean Abou Samra <=
- Re: RFC: stop doing "grand replace" updates to copyright years, Luca Fascione, 2023/02/15
Re: RFC: stop doing "grand replace" updates to copyright years, Jean Abou Samra, 2023/02/22
Re: RFC: stop doing "grand replace" updates to copyright years, Janneke Nieuwenhuizen, 2023/02/13