Groups > linux.debian.bugs.dist > #984602

Bug#943785: RFS: python-pyjsparser (ITP bug #943785)

From	Peter Wienemann <fossdev@posteo.de>
Newsgroups	linux.debian.bugs.dist, linux.debian.maint.python
Subject	Bug#943785: RFS: python-pyjsparser (ITP bug #943785)
Date	2019-11-24 12:30 +0100
Message-ID	<z5Y5P-2Z7-1@gated-at.bofh.it> (permalink)
References	(1 earlier) <yWFOO-4xu-29@gated-at.bofh.it> <z0I1H-1p5-3@gated-at.bofh.it> <z1nex-3V5-1@gated-at.bofh.it> <yWFOO-4xu-29@gated-at.bofh.it> <z1nex-3V5-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

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

Thread

RFS: python-pyjsparser (ITP bug #943785) Peter Wienemann <fossdev@posteo.de> - 2019-11-01 11:00 +0100
  Re: RFS: python-pyjsparser (ITP bug #943785) Nick Morrott <knowledgejunkie@gmail.com> - 2019-11-10 00:10 +0100
    Bug#943785: RFS: python-pyjsparser (ITP bug #943785) Peter Wienemann <fossdev@posteo.de> - 2019-11-11 20:10 +0100
      Bug#943785: RFS: python-pyjsparser (ITP bug #943785) Peter Wienemann <fossdev@posteo.de> - 2019-11-24 12:30 +0100
      Bug#943785: RFS: python-pyjsparser (ITP bug #943785) Peter Wienemann <fossdev@posteo.de> - 2019-12-14 09:20 +0100

csiph-web