From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18422 invoked by alias); 28 Jan 2014 11:58:31 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 18412 invoked by uid 89); 28 Jan 2014 11:58:30 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 28 Jan 2014 11:58:30 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 3F53F1164DA; Tue, 28 Jan 2014 06:58:28 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YleHEX+WYQgE; Tue, 28 Jan 2014 06:58:28 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id CE7E01164D0; Tue, 28 Jan 2014 06:58:27 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 459D1E05A2; Tue, 28 Jan 2014 15:58:24 +0400 (RET) Date: Tue, 28 Jan 2014 11:58:00 -0000 From: Joel Brobecker To: Siva Chandra Cc: gdb-patches Subject: Re: [Patch v8] Debug methods using GDB Python Message-ID: <20140128115824.GF4101@adacore.com> References: <20140128113253.GE4101@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-01/txt/msg00994.txt.bz2 > I have fixed it locally now. Should come out correctly in v9. [...] > None of the new files were committed to the repo ever. But, most of > them were posted for review in 2013. Should they still have 2013-2014 > range in the Copyright notice? Yes, that's correct. When I asked the FSF about it, the answer was that as long as it was saved somewhere, the range should include that year. The year when it actually gets committed to the FSF repo isn't really relevant in that case. Thank you! -- Joel