Revision: 835
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=835
Author:   ineiev
Date:     2025-07-01 14:14:16 -0400 (Tue, 01 Jul 2025)
Log Message:
-----------
add ids

Modified Paths:
--------------
    trunk/sviki/ValidNotices.mdwn

Modified: trunk/sviki/ValidNotices.mdwn
===================================================================
--- trunk/sviki/ValidNotices.mdwn       2025-06-07 10:15:45 UTC (rev 834)
+++ trunk/sviki/ValidNotices.mdwn       2025-07-01 18:14:16 UTC (rev 835)
@@ -1,6 +1,6 @@
 # Copyright and license notices
 
-## Copyrightable files
+## Copyrightable files {#copyrightable}
 
 For copyright purpose, any file more than ten lines long is nontrivial,
 so it should have copyright and license notices.
@@ -11,7 +11,7 @@
 <http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html>
 for further information.
 
-## Legal notices
+## Legal notices {#legal-notices}
 
 Free software licenses rely on copyright law. The pro is that they are
 enforceable. The con is that you get the administrative burden.
@@ -38,7 +38,7 @@
 is worth reading (although some parts are specific to GNU packages):
 <http://www.gnu.org/prep/maintain/html_node/Legal-Matters.html>
 
-## GNU AGPL, GNU GPL, GNU LGPL
+## GNU AGPL, GNU GPL, GNU LGPL {#gnu-licenses}
 
 In order to release your project properly and unambiguously under the
 GNU AGPL, GNU GPL, or GNU LGPL, please place copyright notices and license
@@ -65,7 +65,7 @@
 example, see
 <http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude>.
 
-## GFDL
+## GFDL {#fdl}
 
 In order to release your project properly and unambiguously under the
 GFDL, please place copyright notices and permission-to-copy statements
@@ -79,12 +79,12 @@
 also covers additional points, including a smaller notice that you can
 use in auxiliary files.
 
-## Other licenses
+## Other licenses {#other-licenses}
 
 If the license is small (such as the Modified BSD, X11 or Expat), instead of
 a license notice, include it entirely at the top of all your files.
 
-## Public domain
+## Public domain {#public-domain}
 
 If the files in question are public domain, instead of copyright and
 license notices, include a note saying it's public domain, listing


Reply via email to