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, 02 Sep 2005 15:50:29 -0400

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        05/09/02 19:50:29

Modified files:
        infra/elisp    : savannah.el 

Log message:
        Precised that not only source code needs notices.

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

Patches:
Index: administration/infra/elisp/savannah.el
diff -u administration/infra/elisp/savannah.el:1.36 
administration/infra/elisp/savannah.el:1.37
--- administration/infra/elisp/savannah.el:1.36 Sun Aug 21 09:57:24 2005
+++ administration/infra/elisp/savannah.el      Fri Sep  2 19:50:28 2005
@@ -68,7 +68,7 @@
 ;;   lots of changes tracked via CVS, with suggestions or patches from
 ;;   Jonathan V. Gonzales and Sebastian Wieseler.
 ;;
-;; $Id: savannah.el,v 1.36 2005/08/21 09:57:24 Beuc Exp $
+;; $Id: savannah.el,v 1.37 2005/09/02 19:50:28 Beuc Exp $
 
 ;;
 ;; General
@@ -191,7 +191,7 @@
 
 We wish to review your source code, even if it is not functional, to catch 
potential legal issues early.
 
-For example, to release your program properly under the GNU GPL you must 
include a copyright notice and permission-to-copy statements at the beginning 
of every file of source code.  This is explained in 
http://www.gnu.org/licenses/gpl-howto.html.  Our review would help catch 
potential omissions such as these.\n\n")
+For example, to release your program properly under the GNU GPL you must 
include a copyright notice and permission-to-copy statements at the beginning 
of every file of source code (and other non-trivial files you place under that 
license).  This is explained in http://www.gnu.org/licenses/gpl-howto.html.  
Our review would help catch potential omissions such as these.\n\n")
   (message "Inserted sv-problem-tarball text.")
   )
 
@@ -202,7 +202,7 @@
 (defun sv-problem-gpl-info ()
   (interactive)
   ""
-  (insert "In order to release your project properly and unambiguously under 
the GNU GPL, please place copyright notices and permission-to-copy statements 
at the beginning of every file of source code.
+  (insert "In order to release your project properly and unambiguously under 
the GNU GPL, please place copyright notices and permission-to-copy statements 
at the beginning of every file of source code (and other non-trivial files you 
place under that license).
 
 In addition, if you haven't already, please include a copy of the plain text 
version of the GPL, available from http://www.gnu.org/licenses/gpl.txt, into a 
file named \"COPYING\".
 
@@ -221,7 +221,7 @@
 (defun sv-problem-lgpl-info ()
   (interactive)
   ""
-  (insert "In order to release your project properly and unambiguously under 
the LGPL, please place copyright notices and permission-to-copy statements at 
the beginning of every file of source code.
+  (insert "In order to release your project properly and unambiguously under 
the LGPL, please place copyright notices and permission-to-copy statements at 
the beginning of every file of source code (and other non-trivial files you 
place under that license).
 
 In addition, if you haven't already, please include a copy of the plain text 
version of the GNU LGPL, available from http://www.gnu.org/licenses/lgpl.txt, 
into a file named \"COPYING\".
 




reply via email to

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