Suggestions for in depth discussion of GPLv2§2(a)
GPLv2§2(a) is mentioned quite cursorily. Olly Betts suggests more coverage here might useful on IRC. I noted some ideas after he suggested it.
This commit is contained in:
parent
ec2abce021
commit
555a72beb1
1 changed files with 10 additions and 0 deletions
10
gpl-lgpl.tex
10
gpl-lgpl.tex
|
@ -1548,6 +1548,16 @@ here as well. However, there are three additional requirements.
|
||||||
|
|
||||||
\subsection{The Simpler Parts of GPLv2~\S2}
|
\subsection{The Simpler Parts of GPLv2~\S2}
|
||||||
|
|
||||||
|
% FIXME: GPLv2~\S2(a) isn't discussed heavily here and more should be
|
||||||
|
% discussed about it. There have been developer questions. One idea I had
|
||||||
|
% was to write up:
|
||||||
|
% http://ebb.org/bkuhn/blog/2011/03/11/linux-red-hat-gpl.html
|
||||||
|
% as a compliance case study specific to GPLv2 Section 2(a)
|
||||||
|
%
|
||||||
|
% Another point to discuss here -- or maybe it goes better in the compliance
|
||||||
|
% case study ? -- is to explain that git logs ARE adequate but possibly
|
||||||
|
% overkill.
|
||||||
|
|
||||||
The first (GPLv2~\S2(a)) requires that modified files carry ``prominent
|
The first (GPLv2~\S2(a)) requires that modified files carry ``prominent
|
||||||
notices'' explaining what changes were made and the date of such
|
notices'' explaining what changes were made and the date of such
|
||||||
changes. This section does not prescribe some specific way of
|
changes. This section does not prescribe some specific way of
|
||||||
|
|
Loading…
Reference in a new issue