update year in copyright for README
PATCH 1/1 update year in copyright for README
From: Christian Hesse <[email protected]...>
This line has not been touched in a long time... Let's update the copyright with recent year for README.
--- README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
README +1 -1
@@ -1,6 +1,6 @@ OpenVPN -- A Secure tunneling daemon -Copyright (C) 2002-2010 OpenVPN Technologies, Inc. This program is free software; +Copyright (C) 2002-2016 OpenVPN Technologies, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2 as published by the Free Software Foundation.
Signature · 1 line
2.10.2
Hi,
Quoted 4 lines · Christian Hesse
From: Christian Hesse <[email protected]...>
This line has not been touched in a long time... Let's update the copyright with recent year for README.
I'm fine with merging these, but... could you send a combined copyright-date-updating patch for *all* occurances, please?
Each patch that is merged is a few minutes work which should be spent thoughtfully :-)
gert
Signature · 4 lines
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]...
fax: +49-89-35655025 [email protected]...Hi,
Quoted 12 lines · Gert Doering
Quoted 4 lines · Christian Hesse
From: Christian Hesse <[email protected]...>
This line has not been touched in a long time... Let's update the copyright with recent year for README.
I'm fine with merging these, but... could you send a combined copyright-date-updating patch for *all* occurances, please?
Each patch that is merged is a few minutes work which should be spent thoughtfully :-)
IANL, but looks like the year update is just for "optics". Technically the first year of publication should be enough, isn't it? Anyway updating Copyright 2002-2010 to 2002-2016 would mean some changes where made in 2016 which is true for README, but tedious to figure out for each and every file.
A simpler approach would be to update it only COPYING and let people who do substantial edits to a file update copyright at that time if they feel the urge...
Selva
Gert Doering <[email protected]...> on Thu, 2016/12/01 18:39:
Quoted 10 lines
Hi,
Quoted 4 lines · Christian Hesse
From: Christian Hesse <[email protected]...>
This line has not been touched in a long time... Let's update the copyright with recent year for README.
I'm fine with merging these, but... could you send a combined copyright-date-updating patch for *all* occurances, please?
I will stop here. ;) Did not want to annoy anybody.
IMHO README and program output are valid for the whole project, so it makes sense to update these. No need to update all and every occurrence.
Quoted 2 lines
Each patch that is merged is a few minutes work which should be spent thoughtfully :-)
Agreed. :D Sorry, I should have checked the README file when I prepared the first patch.
Signature · 3 lines
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}Quoted 5 lines · Gert Doering
Hi,
Quoted 2 lines · Christian Hesse
From: Christian Hesse <[email protected]...>
Quoted 8 lines
Quoted 2 lines
This line has not been touched in a long time... Let's update the copyright with recent year for README.
I'm fine with merging these, but... could you send a combined copyright-date-updating patch for *all* occurances, please?
Each patch that is merged is a few minutes work which should be spent thoughtfully :-)
I suggest we take a quick evaluation of updating the copyrights in all files when we're doing the re-indenting task. Whether we blend the copyright update into the patches doing re-indenting, or as a separate patch ... that's a different discussion (which we can agree upon on a developers meeting or just on the #openvpn-devel channel whenever).
Signature · 4 lines
kind regards, David Sommerseth OpenVPN Technologies, Inc