savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] administration/infra/elisp savannah.el


From: Sylvain Beucler
Subject: [Savannah-cvs] administration/infra/elisp savannah.el
Date: Fri, 27 May 2005 16:31:13 -0400

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        05/05/27 20:31:13

Modified files:
        infra/elisp    : savannah.el 

Log message:
        Fixed fsf address canned text, added how to add notices to binary files

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/infra/elisp/savannah.el.diff?tr1=1.27&tr2=1.28&r1=text&r2=text

Patches:
Index: administration/infra/elisp/savannah.el
diff -u administration/infra/elisp/savannah.el:1.27 
administration/infra/elisp/savannah.el:1.28
--- administration/infra/elisp/savannah.el:1.27 Fri May 27 20:24:42 2005
+++ administration/infra/elisp/savannah.el      Fri May 27 20:31:13 2005
@@ -65,7 +65,7 @@
 ;;   sv-closing-resubmit, and added sv-deleted-pending and
 ;;   sv-problem-fdl-info.
 ;;
-;; $Id: savannah.el,v 1.27 2005/05/27 20:24:42 frank_org Exp $
+;; $Id: savannah.el,v 1.28 2005/05/27 20:31:13 Beuc Exp $
 
 ;;
 ;; General
@@ -203,6 +203,8 @@
 
 For more information, see http://www.gnu.org/licenses/gpl-howto.html.
 
+If some of your files cannot carry such notices (e.g. binary files), then you 
can add a README file in the same directory containing the copyright and 
license notices. Check 
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for further 
information.
+
 The GPL FAQ explains why these procedures must be followed.  To learn why a 
copy of the GPL must be included with every copy of the code, for example, see 
http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.\n\n";)
   (message "Inserted sv-problem-gpl-info text.")
   )
@@ -218,6 +220,8 @@
 
 In addition, if you haven't already, please include a copy of the plain text 
version of the LGPL, available from http://www.gnu.org/licenses/lgpl.txt, into 
a file named \"COPYING\".
 
+If some of your files cannot carry such notices (e.g. binary files), then you 
can add a README file in the same directory containing the copyright and 
license notices. Check 
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for further 
information.
+
 For more information, see http://www.gnu.org/licenses/lgpl.html#SEC4.\n\n";)
   (message "Inserted sv-problem-lgpl-info text.")
   )
@@ -270,13 +274,13 @@
 
 Please update your license notices.
 
-Updates versions of the GPL, LGPL and GFDL can also be found at:
+Please update the copy of the license (usually, the 'COPYING' file) in your 
package as well.
+
+Updated versions of the GPL, LGPL and GFDL can also be found at:
 http://www.gnu.org/licenses/gpl.txt
 http://www.gnu.org/licenses/lgpl.txt
 http://www.gnu.org/licenses/fdl.txt
 
-Please update the copy of the license (usually, the 'COPYING' file) in your 
package as well.
-
 You can find some background and a possible migration script at 
https://savannah.gnu.org/forum/forum.php?forum_id=3766
 \n\n")
   (message "Inserted sv-problem-fsf-address text.")




reply via email to

[Prev in Thread] Current Thread [Next in Thread]