From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id C2D9F3858C60 for ; Mon, 10 Jan 2022 17:29:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C2D9F3858C60 Received: from [2001:470:142:3::e] (port=51700 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n6yU1-0002c2-Vk; Mon, 10 Jan 2022 12:29:25 -0500 Received: from [87.69.77.57] (port=2854 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n6yU2-0000E8-0O; Mon, 10 Jan 2022 12:29:26 -0500 Date: Mon, 10 Jan 2022 19:29:17 +0200 Message-Id: <83bl0ja49e.fsf@gnu.org> From: Eli Zaretskii To: Daniel Black Cc: brobecker@adacore.com, gdb-patches@sourceware.org In-Reply-To: (message from Daniel Black via Gdb-patches on Mon, 10 Jan 2022 17:47:49 +1100) Subject: Re: [PATCH 3/6] Manual copyright year update of various GDB files References: <20220101151250.35116-1-brobecker@adacore.com> <20220101151250.35116-4-brobecker@adacore.com> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2022 17:29:28 -0000 > Date: Mon, 10 Jan 2022 17:47:49 +1100 > X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, > DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, RCVD_IN_DNSWL_NONE, > SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 > From: Daniel Black via Gdb-patches > Cc: gdb-patches@sourceware.org > > On Mon, Jan 10, 2022 at 4:37 PM Joel Brobecker wrote: > > > > > On Sun, Jan 2, 2022 at 2:14 AM Joel Brobecker via Gdb-patches > > > wrote: > > > > > > > gdb/doc/refcard.tex | 4 ++-- > > > > > > How do you claim new copyright in this file when the last > > > (non-copyright notice) change was in 2012 (168997566e2a)? > > > > > > The other files seem reasonable based on the frequency of changes. > > > > Unfortunately, I am not a lawyer and cannot answer your question. > > We are applying here our understanding here of what we were told > > by the FSF we could do. > > It doesn't seem right (ref: "The copyright notice" > http://www.gnu.org/licenses/gpl-howto.html). > Replacing "release" for "file" as equivalent copyrightable object > would be when the last change ("creative work") was written > to the file as the minimum criteria. > > "For software with several releases .. use a range (“2008-2010”) ... > if and only if every year in the range, inclusive, really is a > “copyrightable” year that would be listed individually; and ... > > The non-legal, but endorsed, and not (publicly/locally) contended > verbose description: > > https://softwareengineering.stackexchange.com/questions/210472/is-renewal-of-mit-license-needed-on-github-at-the-beginning-of-each-year > > A pre-release/end of year process that accounts for changes would seem > more respectful of what copyright is, in my not-a-lawyer opinion > anyway. We work according to the FSF copyright lawyers, and they tell us to add a new year each year. This is a policy used by the entire GNU project. If you want to change that, please take it up with the FSF lawyers. We are not qualified to discuss this stuff here.