Copyleft/guide Changeset - 59bff741f28b

Changeset - 59bff741f28b

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Bradley Kuhn (bkuhn) - 10 years ago 2014-03-19 14:00:54
bkuhn@ebb.org

Small formatting fixes in this paragraph.

1 file changed with 2 insertions and 2 deletions:

gpl-lgpl.tex

0 comments (0 inline, 0 general)

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
   ``Complete Corresponding Source''.  Meanwhile, use of the acronym ``CCS''
   (sometimes, ``C&CS'') was so widespread among GPL enforcers that its use
   continues even though GPLv3-focused experts tend to say just the defined
   term of ``Corresponding Source''.}, or, as GPLv3 officially calls it,
 ``Corresponding Source'', is given in GPLv3~\S1\P4.  This definition is as
 broad as necessary to protect users' exercise of their rights under the
 GPL. We follow the definition with particular examples to remove any doubt
 that they are to be considered Complete Corresponding Source Code. We wish to
 GPL\@.  We follow the definition with particular examples to remove any doubt
 that they are to be considered Complete Corresponding Source Code.  We wish to
 make completely clear that a licensee cannot avoid complying with the
 requirements of the GPL by dynamically linking an add-on component to the
 original version of a program.
 Though the definition of Complete Corresponding Source Code in the
 second paragraph of section 1 is expansive, it is not sufficient to

0 comments (0 inline, 0 general)