André Roth <neolynx@xxxxxxxxx> writes: > On Tue, 25 Mar 2014 21:51:49 +0100 > Bjørn Mork <bjorn@xxxxxxx> wrote: > >> > - * Copyright (c) 2011-2012 - Mauro Carvalho Chehab >> > - * Copyright (c) 2012 - Andre Roth <neolynx@xxxxxxxxx> >> > + * Copyright (c) 2013 - Andre Roth <neolynx@xxxxxxxxx> >> > * >> > * This program is free software; you can redistribute it and/or >> > * modify it under the terms of the GNU General Public License >> >> This copyright change looked strange to me. Accidental deletion? > > Hi Bjørn, > > thanks for pointing this out. > originally I was adding mauro to my dvb files as the "owner" of dvb in > v4l. mauro then stated on some files that this was not his code and as > the PMT is originally my code, I corrected this here. > > @mauro: please correct me if I'm wrong... Correcting the copyright is of course fine, but I think it would be good to document that in the patch description so people like me don't end up asking unnecessary questions :-) > I'm a bit confused about the copyright year and author. Is this still > needed in the age of git ? What is the policy for them ? IANAL. But looking at this from a practical point of view, I believe that this info is useful whether it is required or not. Reading the copyright owner(s) out of a git log can be a lot of work, and it isn't necessariliy correct either - your copyright can be assigned to e.g. your employer or to the FSF. It's also difficult to judge who of many contributors have made changes big enough to make them copyright owners. Some changes can be small in code size but still major, while other changes can touch almost every line but still only be a minor editorial fixup. And why is it useful who owns a copyright and when the copyrighted work was produced? If relicensing your code ever becomes a question, then we need to know who to contact. You might think that relicensing isn't going to happen. But there are real world examples where code has ended up beeing linked to libraries with a GPL conflicting license, and therefore needed an exception. The classical example is linking with openssl. And the year is useful because copyright expires some years (depending on country of origin, but typical 50) after the authors death. You write code that will live forever, right? :-) Bjørn -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
