Path: csiph.com!weretis.net!feeder6.news.weretis.net!feeder7.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Peter Wienemann Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python Subject: Bug#943785: RFS: python-pyjsparser (ITP bug #943785) Date: Sun, 24 Nov 2019 12:30:02 +0100 Message-ID: References: X-Original-To: Nick Morrott X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Sun Nov 24 11:21:08 2019 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -3.75 Reply-To: Peter Wienemann , 943785@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: wnpp@debian.org X-Debian-Pr-Message: followup 943785 X-Debian-Pr-Package: wnpp X-Spam-Bayes: score:0.0000 Tokens: new, 13; hammy, 145; neutral, 32; spammy, 0. spammytokens: hammytokens:0.000-+--H*r:posteo.de, 0.000-+--H*RU:posteo.de, 0.000-+--Hx-spam-relays-external:posteo.de, 0.000-+--Hx-spam-relays-external:customer, 0.000-+--H*RU:submission Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1574594199; bh=WhopLMeumuBYkE7dEZc0WdF3U+ZGniArIyGsoB3+QQQ=; h=Subject:From:To:Cc:Date:From; b=YUUbXsS84/yAzZe5he7nI+qCDlj1zdp/8zv+DnjE0ebjCdTUFOfzjYS/iEGwWTPmY VZ3mNNr6Q8vPxgPj6ojumNHJCZybzvMGMSCtSuamfhBJkMJfmvbA4+rGIGvcJeEMVD 8azjFyM3qsKwR2HX00hZt7ErHeFG2ykMv3/fMVFHywmfkJjhU1HjAlevArvEV+BSMY n6VjZpG8eLPjvonyN6aMMsrB52woC33w/qjrR0QZjNja3o+SWDh5JNYuTkQKY/efgY /nZ4+HzhA+YbJVfQfia3CdAZej/z/6F6Q9DFcbR7FowYb7Wjbt8HBSe7Wo6PxnbE8n ZRmWZiN4uRM+g== User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Debian-Message: from BTS X-Mailing-List: archive/latest/1570769 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 18 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: 943785@bugs.debian.org, debian-python X-Original-Date: Sun, 24 Nov 2019 12:16:30 +0100 X-Original-Message-ID: <733728e4-28ab-c8b0-54ed-cd7d6d928cf9@posteo.de> X-Original-References: <63cf3f6c-e1e6-4ea6-ff28-790291c737f4@posteo.de> <157237831776.29447.14167943616916178893.reportbug@emil.localdomain> <157237831776.29447.14167943616916178893.reportbug@emil.localdomain> Xref: csiph.com linux.debian.bugs.dist:984602 linux.debian.maint.python:12038 Hi Nick, On 11.11.19 20:01, Peter Wienemann wrote: >> * d/copyright >> - the only copyright dates I can see in the source are 2014-2015 > > Judging from the source files, you are right. Judging from the git > commit history I see commits between 2015 and 2019. What is a better > guideline for copyright years: copyright notices in the source or the > git history? Maybe it would be best to combine both information which > would yield 2014-2019. Once I know what should be used, I will update > the copyright file accordingly. I asked on IRC how to handle this situation. The answer was: Use the copyright years from the copyright notices in the source. I have just pushed a commit with the corresponding change to salsa. Peter