Properly quote the & in C&CS. HT tmarble.
<tmarble> note: might need to escape the & in C&CS [12:05]
This commit is contained in:
parent
7090007b0d
commit
366854aaf1
1 changed files with 1 additions and 1 deletions
|
@ -2386,7 +2386,7 @@ throughout the text of GPLv2, the definition of CCS\footnote{Note that the
|
||||||
instead). However, both GPLv2 and the early drafts of GPLv3 itself used
|
instead). However, both GPLv2 and the early drafts of GPLv3 itself used
|
||||||
the word complete, and early GPLv3 drafts even included the phrase
|
the word complete, and early GPLv3 drafts even included the phrase
|
||||||
``Complete Corresponding Source''. Meanwhile, use of the acronym ``CCS''
|
``Complete Corresponding Source''. Meanwhile, use of the acronym ``CCS''
|
||||||
(sometimes, ``C&CS'') was so widespread among GPL enforcers that its use
|
(sometimes, ``C\&CS'') was so widespread among GPL enforcers that its use
|
||||||
continues even though GPLv3-focused experts tend to say just the defined
|
continues even though GPLv3-focused experts tend to say just the defined
|
||||||
term of ``Corresponding Source''.}, or, as GPLv3 officially calls it,
|
term of ``Corresponding Source''.}, or, as GPLv3 officially calls it,
|
||||||
``Corresponding Source'', is given in GPLv3~\S1\P4. This definition is as
|
``Corresponding Source'', is given in GPLv3~\S1\P4. This definition is as
|
||||||
|
|
Loading…
Reference in a new issue