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

[Sylvain Beucler]

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        06/01/08 13:28:02

Modified files:
        infra/elisp    : savannah.el 

Log message:
        Removed the part that seem to imply that the registration is private
        Added a precision about a misconception of 'release'.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/administration/administration/infra/elisp/savannah.el.diff?tr1=1.41&tr2=1.42&r1=text&r2=text

Patches:
Index: administration/infra/elisp/savannah.el
diff -u administration/infra/elisp/savannah.el:1.41 
administration/infra/elisp/savannah.el:1.42
--- administration/infra/elisp/savannah.el:1.41 Fri Dec  2 13:24:34 2005
+++ administration/infra/elisp/savannah.el      Sun Jan  8 13:28:02 2006
@@ -73,7 +73,7 @@
 ;;   lots of changes tracked via CVS, with suggestions or patches from
 ;;   Jonathan V. Gonzales and Sebastian Wieseler.
 ;;
-;; $Id: savannah.el,v 1.41 2005/12/02 13:24:34 Beuc Exp $
+;; $Id: savannah.el,v 1.42 2006/01/08 13:28:02 Beuc Exp $
 
 ;;
 ;; General
@@ -192,11 +192,13 @@
 (defun sv-problem-tarball ()
   (interactive)
   ""
-  (insert "Please include a \(perhaps temporary\) URL pointing to the source 
code.  The description you gave when registering will not be read by the 
general public.  If you are still concerned with privacy, however, you can 
forward the code to me by email.
+  (insert "Please include a \(perhaps temporary\) URL pointing to the source 
code. Alternatively, you can forward the code to me by email.
 
 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  copyrightable file, usually any file more than 10 lines long.  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  copyrightable file, usually any file more than 10 lines long.  This 
is explained in http://www.gnu.org/licenses/gpl-howto.html.  Our review would 
help catch potential omissions such as these.
+
+Note that sending code to our repositories _is_ a release, since the code will 
then be publicly available through anonymous.\n\n")
   (message "Inserted sv-problem-tarball text.")
   )