Re: Update copyright for 2016/17 files, and script (issue 320390043 by g...@ursliska.de)

2017-03-23 Thread Hans Ã…berg
> On 23 Mar 2017, at 11:18, Andrew Bernard wrote: > My understanding of copyright is that the date range applies to the > published work as a whole, and does not operate on the granularity of > individual components. I am told there should be all years it has been published. > Furthermore, the

Re: Update copyright for 2016/17 files, and script (issue 320390043 by g...@ursliska.de)

2017-03-23 Thread Andrew Bernard
Hi Urs, My understanding of copyright is that the date range applies to the published work as a whole, and does not operate on the granularity of individual components. Furthermore, there is no legal requirement to actually have a copyright notice at all, as works are naturally copyright nowadays,

Re: Update copyright for 2016/17 files, and script (issue 320390043 by g...@ursliska.de)

2017-03-23 Thread Werner LEMBERG
> So if we do have a script that automatically updates only changed > files nothing speaks against using it, isn't it? Well, yes, but I don't see an advantage. Today, using gitk or something similar, you can very easily track changes. Having identical copyright notices in all files of lilypond

Re: Update copyright for 2016/17 files, and script (issue 320390043 by g...@ursliska.de)

2017-03-23 Thread Urs Liska
Am 23.03.2017 um 08:19 schrieb Werner LEMBERG: >> Unfortunately I don't find a link right now, but it is my >> understanding that the copyright notice should only be updated to >> files that have actually been modified. > AFAIK, this is not correct. The copyright is applied to the *package* > li

Re: Update copyright for 2016/17 files, and script (issue 320390043 by g...@ursliska.de)

2017-03-23 Thread Werner LEMBERG
> Unfortunately I don't find a link right now, but it is my > understanding that the copyright notice should only be updated to > files that have actually been modified. AFAIK, this is not correct. The copyright is applied to the *package* lilypond, so if *any* file changes, the copyright notice

Re: Update copyright for 2016/17 files, and script (issue 320390043 by g...@ursliska.de)

2017-03-23 Thread Urs Liska
Am 23.03.2017 um 01:50 schrieb gra...@percival-music.ca: > Could you separate the "Run script xyz" changes from the changes to > script(s)? That would help to see exactly what's happening here. Yes, I'll do so, but this patch isn't really intended to be merged as-is anyway. > > > https://coder

Update copyright for 2016/17 files, and script (issue 320390043 by g...@ursliska.de)

2017-03-22 Thread graham
Could you separate the "Run script xyz" changes from the changes to script(s)? That would help to see exactly what's happening here. https://codereview.appspot.com/320390043/diff/1/scripts/auxiliar/update-copyright.sh File scripts/auxiliar/update-copyright.sh (right): https://codereview.appspo