[Top][All Lists]
[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: |
Wed, 01 Jun 2005 16:08:37 -0400 |
CVSROOT: /cvsroot/administration
Module name: administration
Branch:
Changes by: Sylvain Beucler <address@hidden> 05/06/01 20:08:37
Modified files:
infra/elisp : savannah.el
Log message:
Added 'GNU' in front 'GPL' and reworded sv-approve-as-nongnu to match
http://www.gnu.org/help/evaluation.html
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/infra/elisp/savannah.el.diff?tr1=1.30&tr2=1.31&r1=text&r2=text
Patches:
Index: administration/infra/elisp/savannah.el
diff -u administration/infra/elisp/savannah.el:1.30
administration/infra/elisp/savannah.el:1.31
--- administration/infra/elisp/savannah.el:1.30 Wed Jun 1 06:20:51 2005
+++ administration/infra/elisp/savannah.el Wed Jun 1 20:08:36 2005
@@ -65,7 +65,7 @@
;; sv-closing-resubmit, and added sv-deleted-pending and
;; sv-problem-fdl-info.
;;
-;; $Id: savannah.el,v 1.30 2005/06/01 06:20:51 Beuc Exp $
+;; $Id: savannah.el,v 1.31 2005/06/01 20:08:36 Beuc Exp $
;;
;; General
@@ -186,7 +186,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 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. 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.")
)
@@ -197,7 +197,7 @@
(defun sv-problem-gpl-info ()
(interactive)
""
- (insert "In order to release your project properly and unambiguously under
the 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.
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\".
@@ -218,7 +218,7 @@
""
(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.
-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\".
+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\".
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.
@@ -233,7 +233,7 @@
(defun sv-problem-fdl-info ()
(interactive)
""
- (insert "In order to release your project properly and unambiguously under
the FDL, please place copyright notices and permission-to-copy statements after
the title page of each work.
+ (insert "In order to release your project properly and unambiguously under
the GFDL, please place copyright notices and permission-to-copy statements
after the title page of each work.
In addition, if you haven't already, please add a copy of the FDL (available
from http://www.gnu.org/licenses/fdl.html in various formats) as a section of
your works , and as plain text in a file named 'COPYING'
(http://www.gnu.org/licenses/fdl.txt).
@@ -534,7 +534,7 @@
""
(insert "Hi,
-I have approved your project as non-GNU. You will receive an automated e-mail
containing detailed information about the approval. If you want your project to
be evaluated for inclusion in the GNU project, please contact the GNU Eval
team, following the instructions at http://www.gnu.org/help/evaluation.html .
+I have approved your project as non-GNU. You will receive an automated e-mail
containing detailed information about the approval. If you would like to offer
your project to the GNU project, please contact the GNU Eval team, following
the instructions at http://www.gnu.org/help/evaluation.html .
Regards.\n")
(message "Inserted sv-approve-as-nongnu text.")