From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id B11223851C2A for ; Wed, 13 May 2020 14:42:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B11223851C2A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark@simark.ca Received: from [10.0.0.193] (unknown [192.222.164.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 320451E5F9; Wed, 13 May 2020 10:42:53 -0400 (EDT) Subject: Re: [PATCH] gdb: update the copyright year in async-event.[ch] To: Tankut Baris Aktemur , gdb-patches@sourceware.org Cc: tom@tromey.com References: <1589374645-27571-1-git-send-email-tankut.baris.aktemur@intel.com> From: Simon Marchi Message-ID: <4b3a81dd-2676-3075-1100-b33ad60b9c66@simark.ca> Date: Wed, 13 May 2020 10:42:52 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <1589374645-27571-1-git-send-email-tankut.baris.aktemur@intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: tl Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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: Wed, 13 May 2020 14:42:54 -0000 On 2020-05-13 8:57 a.m., Tankut Baris Aktemur via Gdb-patches wrote: > The async-event.[ch] files were introduced recently as a result of > splitting the event-loop. I believe the copyright year update was > just an oversight. So, this patch fixes that. Thanks, this is ok (and could probably be considered obvious). Simon