[Top][All Lists]

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

gnustandards ChangeLog maintain.texi

From: Karl Berry
Subject: gnustandards ChangeLog maintain.texi
Date: Thu, 28 May 2009 16:44:35 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       09/05/28 16:44:35

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        revised second sentence of GAP about no warranty for brevity, approved 
by lawyers


Index: ChangeLog
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -b -r1.95 -r1.96
--- ChangeLog   29 Apr 2009 17:02:23 -0000      1.95
+++ ChangeLog   28 May 2009 16:44:35 -0000      1.96
@@ -1,3 +1,9 @@
+2009-05-28  Karl Berry  <address@hidden>
+       * maintain.texi (License Notices for Other Files): second sentence
+       about no warranty revised to be shorter, per legal advice.
+       (Copyright Notices): use @file for filenames, for consistency.
 2009-04-29  Karl Berry  <address@hidden>
        * maintain.texi (License Notices for Other Files): second sentence

Index: maintain.texi
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.173
retrieving revision 1.174
diff -u -b -r1.173 -r1.174
--- maintain.texi       29 Apr 2009 17:02:24 -0000      1.173
+++ maintain.texi       28 May 2009 16:44:35 -0000      1.174
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate April 29, 2009
address@hidden lastupdate May 26, 2009
 @c %**end of header
 @dircategory GNU organization
@@ -526,9 +526,9 @@
 that it is in the public domain.
 Even image files and sound files should contain copyright notices and
-license notices, if they can.  Some formats do not have room for textual
-annotations; for these files, state the copyright and copying
-permissions in a README file in the same directory.
+license notices, if their format permits.  Some formats do not have
+room for textual annotations; for these files, state the copyright and
+copying permissions in a @file{README} file in the same directory.
 Change log files should have a copyright notice and license notice at
 the end, since new material is added at the beginning but the end
@@ -759,16 +759,20 @@
 @subsection License Notices for Other Files
 Small supporting files, short manuals (under 300 lines long) and rough
-documentation (README files, INSTALL files, etc) can use a simple
-all-permissive license like this one:
+documentation (@file{README} files, @file{INSTALL} files, etc.)@: can
+use a simple all-permissive license like this one:
 Copying and distribution of this file, with or without modification,
 are permitted in any medium without royalty provided the copyright
 notice and this notice are preserved.  This file is offered as-is,
-without warranty of any kind.
+without any warranty.
 @end smallexample
+Older versions of this license did not have the second sentence with
+the express warranty disclaimer.  There is no urgent need to update
+existing files, but new files should use the new text.
 If your package distributes Autoconf macros that are intended to be
 used (hence distributed) by third-party packages under possibly
 incompatible licenses, you may also use the above all-permissive

reply via email to

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