1 Copyright (C) 2007, 2008 Free Software Foundation, Inc.
2 See the end of the file for license conditions.
5 NOTES ON COPYRIGHTS AND LICENSES
9 A "copyright notice" consists of one or a few lines of this format:
10 "Copyright (C) 2006, 2007 Free Software Foundation, Inc."
12 A "license notice" is a statement of permissions, and is usually much
13 longer, eg the text "GNU Emacs is free software...".
16 Summary for the impatient:
18 1. Don't add code to Emacs written by someone other than yourself
19 without thinking about the legal aspect. Even if the changes are
20 trivial, consider if they combine with previous changes by the same
21 author to make a non-trivial total. If so, make sure they have an
22 assignment. If adding a whole file adjust the copyright statements in
25 2. When installing code written by someone else, the ChangeLog entry
26 should be in the name of the author of the code, not the person who
27 installs it. I think it is helpful to put the author (if not yourself)
28 in the CVS log as well; and to not install any of your own changes in
31 3. With images, add the legal info to a README file in the directory
34 4. If you add a lot of text to a previously trivial file that had no
35 legal notices, consider if you should add a copyright statement.
37 5. Please don't just add an FSF copyright without checking that is the
41 Every non-trivial file distributed through the Emacs CVS should be
42 self-explanatory in terms of copyright and license. This includes
43 files that are not distributed in Emacs releases (for example, the
44 admin/ directory), because the whole Emacs CVS is publicly
47 The definition of triviality is a little vague, but a rule of thumb is
48 that any file with less than 15 lines of actual content is trivial. If
49 a file is auto-generated (eg ldefs-boot.el) from another one in the
50 CVS, then it does not really matter about adding a copyright statement
51 to the generated file.
53 Legal advice says that we could, if we wished, put a license notice
54 even in trivial files, because copyright law in general looks at the
55 overall work as a whole. It is not _necessary_ to do so, and rms
56 prefers that we do not. This means one needs to take care that trivial
57 files do not grow and become non-trivial without having a license
58 added. NB consequently, if you add a lot of text to a small file,
59 consider whether your changes have made the file worthy of a copyright
60 notice, and if so, please add one.
62 It can be helpful to put a reminder comment at the start of a trivial
63 file, eg: "add a license notice if this grows to > 10 lines of code".
65 The years in the copyright notice should be updated every year (see
66 file "years" in this directory). The PS versions of refcards etc
67 should display copyright notices (an exception to the rule about
68 "generated" files), but these can just display the latest year. The
69 full list of years should be kept in comments in the source file. If
70 these are distributed in CVS, check in a regenerated version when the
71 tex files are updated.
73 Copyright changes should be propagated to any associated repositories
74 (eg Gnus, MH-E), but I think in every case this happens automatically
77 All README (and other such text files) that are non-trivial should
78 contain copyright statements and GPL license notices, exactly as .el
79 files do (see e.g. README in the top-level directory). Before 2007,
80 we used a simple, short statement permitting copying and modification
81 provided legal notices were retained. In Feb 2007 we switched to the
82 standard GPL text, on legal advice. Some older text files in etc/
83 should, however, keep their current licenses (see below for list).
85 For image files, the copyright and license details should be recorded
86 in a README file in each directory with images. (Legal advice says
87 that we need not add notices to each image file individually, if they
88 allow for that.). It is recommended to use the word "convert" to
89 describe the automatic process of changing an image from one format to
90 another (http://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00618.html).
93 When installing a file with an "unusual" license (after checking first
94 it is ok), put a copy of the copyright and license in the file (if
95 possible. It's ok if this makes the file incompatible with its
96 original format, if it can still be used by Emacs), or in a README
97 file in the relevant directory.
99 The vast majority of files are copyright FSF and distributed under the
100 GPL. A few files (mainly related to language and charset support) are
101 copyright AIST alone, or both AIST and FSF. (Contact Kenichi Handa
102 with questions about legal issues in such files.) In all these cases,
103 the copyright years in each file should be updated each year.
105 There are some exceptions to the points in the previous paragraph, and
106 these are listed below for reference, together with any files where
107 the copyright needs to be updated in "unusual" ways.
109 If you find any other such cases, please consult to check they are ok,
110 and note them in this file. This includes missing copyright notices,
111 and "odd" copyright holders. In most cases, individual authors should
112 not appear in copyright statements. Either the copyright has been
113 assigned (check copyright.list) to the FSF (in which case the original
114 author should be removed and the year(s) transferred to the FSF); or
115 else it is possible the file should not be in Emacs at all (please
118 Note that it seems painfully clear that one cannot rely on CVS logs,
119 or even ChangeLogs, for older changes. People often installed changes
120 from others, without recording the true authorship.
122 [For reference, most of these points were established via email with
123 rms, 2007/1, "Copyright years".]
126 lisp/version.el # emacs-copyright
127 lib-src/ebrowse.c # version
128 lib-src/etags.c # print_version
129 lib-src/rcs2log # Copyright
130 Cocoa/Emacs.base/Contents/Info.plist
131 Cocoa/Emacs.base/Contents/Resources/English.lproj/InfoPlist.strings
132 GNUstep/Emacs.base/Resources/Info-gnustep.plist
133 `set-copyright' in admin.el will do all the above.
135 <top-level>/install-sh
137 - this file is copyright MIT, which is OK. Leave the copyright alone.
140 public domain, leave alone.
143 no notices (see below).
146 - update BOTH notices in this file
149 - written by Michael DeCorte, who has no assignment. But trivial
150 enough to not need license.
153 - doesn't need a humorless disclaimer, because Karl Fogel says we
154 can consider it part of Emacs, and he has a blanker disclaimer for
155 Emacs changes. (email to rgm "[Emacs-commit] emacs/etc future-bug",
158 etc/letter.pbm,letter.xpm
159 - trivial, no notice needed.
160 <http://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00324.html>
163 - trivial (at time of writing), no license needed
165 etc/GNU, INTERVIEW, LINUX-GNU, MOTIVATION, SERVICE, THE-GNU-PROJECT,
167 rms: "These are statements of opinion or testimony. Their licenses
168 should permit verbatim copying only. Please don't change the
169 licenses that they have. They are distributed with Emacs but they
170 are not part of Emacs."
173 standard notices. Just a note that although the file itself is not
174 really copyrightable, in the wider context of it being part of
175 Emacs (and written by those with assignments), a standard notice is
179 rms: simple license is fine for this file
181 leim/CXTERM-DIC/4Corner.tit, ARRAY30.tit, CCDOSPY.tit, ECDICT.tit,
182 ETZY.tit, PY-b5.tit, Punct-b5.tit, Punct.tit, QJ-b5.tit, QJ.tit,
183 SW.tit, TONEPY.tit, ZOZY.tit
184 - leave the copyrights alone.
186 leim/MISC-DIC/CTLau-b5.html, CTLau.html, cangjie-table.b5, cangjie-table.cns,
187 pinyin.map, ziranma.cin
188 - leave the copyright alone.
189 Note that pinyin.map, ziranma.cin (and hence the generated
190 leim/quail/PY.el, ZIRANMA.el) are under GPLv1 or later.
192 leim/SKK-DIC/SKK-JISYO.L
194 (the latter is auto-generated from the former). Leave the copyright alone.
197 Copyright information is duplicated in etc/ETAGS.README. Update that
200 Until 2007 etags.c was described as being copyright FSF and Ken Arnold.
201 After some investigation in Feb 2007, then to the best of our
202 knowledge we believe that the original 1984 Emacs version was based
203 on the version in BSD4.2. See for example this 1985 post from Ken Arnold:
204 <http://groups.google.com/group/mod.sources/browse_thread/thread/ffe5c55845a640a9>
205 I have received enough requests for the current source to ctags
206 to post it. Here is the latest version (what will go out with
207 4.3, modulo any bugs fixed during the beta period). It is the
208 4.2 ctags with recognition of yacc and lex tags added.
210 See also a 1984 version of ctags (no copyright) posted to net.sources:
211 <http://groups.google.com/group/net.sources/msg/a21b6c21be12a98d>
212 Version of etags.c in emacs-16.56 duplicates comment typos.
214 Accordingly, in Feb 2007 we added a 1984 copyright for the
215 University of California and a revised BSD license. The terms of
216 this require that the full license details be available in binary
217 distributions - hence the file etc/ETAGS.README. The fact that the
218 --version output just says "Copyright <year> FSF" is apparently OK
219 from a legal point of view.
221 lib-src/getopt1.c, getopt_int.h
222 - these are from the GNU C library. Leave the copyrights alone.
225 - no special rules about the copyright. We note here that we believe
226 (2007/1) there is no problem with our use of the name "tetris" or
228 rms: "My understanding is that game rules as such are not copyrightable."
229 <http://lists.gnu.org/archive/html/emacs-devel/2007-01/msg00960.html>
230 rms: Legal advice is that we are ok and need not worry about this.
234 - there are also copyrights in the body of the file. Update these too.
238 rms (2007/02/17): "lwlib is not assigned to the FSF; we don't consider
239 it part of Emacs. [...] Therefore non-FSF copyrights are ok in lwlib."
241 NB don't change the GPL version used for lwlib .c and .h files (see
244 FSF copyrights should only appear in files which have undergone
245 non-trivial cumulative changes from the original versions in the Lucid
246 Widget Library. NB this means that if you make non-trivial changes to
247 a file with no FSF copyright, you should add one. Also, if changes are
248 reverted to the extent that a file becomes basically the same as the
249 original version, the FSF copyright should be removed.
251 In my (rgm) opinion, as of Feb 2007, all the non-trivial files differ
252 significantly from the original versions, with the exception of
253 lwlib-Xm.h. Most of the changes that were made to this file have
254 subsequently been reverted. Therefore I removed the FSF copyright from
255 this file (which is arguably too trivial to merit a notice anyway). I
256 added FSF copyright to the following files which did not have them
257 already: Makefile.in, lwlib-Xaw.c, lwlib-int.h (borderline),
258 lwlib-utils.c (borderline), lwlib.c, lwlib.h.
260 Copyright years before the advent of public CVS in 2001 were those
261 when I judged (from the CVS logs) that non-trivial amounts of change
262 had taken place. I also adjusted the existing FSF years in xlwmenu.c,
263 xlwmenu.h, and xlwmenuP.h on the same basis.
265 Note that until Feb 2007, the following files in lwlib were lacking
266 notices: lwlib-int.h, lwlib.h, lwlib-Xaw.h, lwlib-Xlw.h, lwlib-utils.h
268 The following files did not list a Lucid copyright: xlwmenu.h,
271 To the best of our knowledge, all the code files in lwlib were
272 originally part of the Lucid Widget Library, even if they did not say
273 so explicitly. For example, they were all present in Lucid Emacs 19.1
274 in 1992. The exceptions are the two Xaw files, which did not appear
275 till Lucid Emacs 19.9 in 1994. The file lwlib-Xaw.h is too trivial to
276 merit a copyright notice, but would presumably have the same one as
277 lwlib-Xaw.c. We have been unable to find a true standalone version of
278 LWL, if there was such a thing, to check definitively.
280 To clarify the situation, in Feb 2007 we added Lucid copyrights and
281 GPL notices to those files lacking either that were non-trivial,
282 namely: lwlib-int.h, lwlib.h, xlwmenu.h, xlwmenuP.h. This represents
283 our best understanding of the legal status of these files. We also
284 clarified the notices in Makefile.in, which was originally the
285 Makefile auto-generated from Lucid's Imakefile.
287 As of Feb 2007, the following files are considered too trivial for
288 notices: lwlib-Xaw.h, lwlib-Xlw.h, lwlib-utils.h.
290 The version of lwlib/ first installed in Emacs seems to be the same as
291 that used in Lucid Emacs 19.8 (released 6-sep-93); except the two Xaw
292 files, which did not appear till Athena support was added in Lucid
293 Emacs 19.9. In Lucid Emacs 19.1, all files were under GPLv1 or later,
294 but by Lucid Emacs 19.8, lwlib.c and xlwmenu.c had been switched to v2
295 or later. These are the versions that were first installed in Emacs.
296 So in GNU Emacs, these two files have been under v2 or later since
299 It seems that it was the intention of Lucid to use v1 or later
300 (excepting the two files mentioned previously); so this is the license
301 we have used when adding notices to code that did not have notices
302 originally. Although we have the legal right to switch to v2 or later,
303 rms prefers that we do not do so.
306 doc/*/doclicense.texi
307 - leave the copyright alone in this imported file.
309 doc/*/*.texi - All manuals should be under GFDL (but see below), and
310 should include a copy of it, so that they can be distributed
311 separately. faq.texi has a different license, for some reason no-one
313 http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00583.html
314 http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00618.html
316 doc/misc/mh-e.texi is dual-licensed (GPL and GFDL) per agreement with
317 FSF (reconfirmed by rms Aug 25 2008). Discussion with
318 licensing@fsf.org starting on Thu, 07 Aug 2003 with subject:
319 "[gnu.org #58812] Changing license of MH-E manual"
322 msdos/is_exec.c, sigaction.c - these files are copyright DJ Delorie.
323 Leave the copyrights alone. Leave the Eli Zaretskii copyright in
324 is_exec.c alone. See the msdos/README file for the legal history of
329 Keep the "copyright.h" method used by X11, rather than moving the
330 licenses into the files. Note that the original X10.h did not use
331 copyright.h, but had an explicit notice, which we retain.
333 If you make non-trivial changes to a file which does not have an FSF
334 notice, add one and a GPL notice (as per Activate.c). If changes to a
335 file are reverted such that it becomes essentially the same as the
336 original X11 version, remove the FSF notice and GPL.
338 Only the files which differ significantly from the original X11
339 versions should have FSF copyright and GPL notices. At time of writing
340 (Feb 2007), this is: Activate.c, Create.c, Internal.c. I (rgm)
341 established this by diff'ing the current files against those in X11R1,
342 and when I found significant differences looking in the ChangeLog for
343 the years they originated (the CVS logs are truncated before 1999). I
344 therefore removed the FSF notices (added in 200x) from the other
345 files. There are some borderline cases IMO: AddSel.c, InsSel.c,
346 XMakeAssoc.c, XMenu.h. For these I erred on the side of NOT adding FSF
349 With regards to whether the files we have changed should have GPL
350 added or not, rms says (2007-02-25, "oldXmenu issues"):
352 It does not make much difference, because oldXmenu is obsolete
353 except for use in Emacs (and it is not normally used in Emacs any
356 So, to make things simple, please put our changes under the GPL.
358 insque.c had no copyright notice until 2005. The version of insque.c
359 added to Emacs 1992-01-27 is essentially the same as insremque.c added
360 to glic three days later by Roland McGrath, with an FSF copyright and
361 GPL, but no ChangeLog entry:
362 <http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/libc/misc/insremque.c?\
363 rev=1.1&cvsroot=glibc>
364 To the best of his recollection, McGrath (who has a copyright
365 assignment) was the author of this file (email from roland at frob.com
366 to rms, 2007-02-23, "Where did insque.c come from?"). The FSF
367 copyright and GPL in this file are therefore correct as far as we
370 Imakefile had no legal info in Feb 2007, but was obviously based on
371 the X11 version (which also had no explicit legal info). As it was
372 unused, I removed it. It would have the same MIT copyright as
373 Makefile.in does now.
377 - contains numerous copyrights from the GNU C library. Leave them alone.
379 src/acldef.h, chpdef.h, ndir.h
380 - see comments below. These files are OK to be released with Emacs
381 22, but we may want to revisit them afterwards.
384 ** Some notes on resolved issues, for historical information only
387 rms: "surely written either by me or by ESR. (If you can figure out
388 which year, I can probably tell you which.) Either way, we have papers
389 for it." It was present in Emacs-16.56 (15-jul-85). rms: "Then I
390 conclude it was written by me."
393 Very obsolete file removed March 2007. Doesn't say who the author
394 is, but web-search suggests Karl Kleinpaste, who has no Emacs
395 assignment. Trivial anyway.
396 http://groups.google.com/group/comp.unix.shell/browse_thread/thread/bf3df496994\
397 9f1df/7e5922c67b3a98fb
398 http://groups.google.com/group/comp.unix.questions/msg/cc7e49cacfd1ccb4
399 (original 1987 source)
402 - had no copyright notice till Feb 2007. ChangeLog.3 suggests it was
403 written by Eric Raymond. When asked by rms on 14 Feb 2007 he said:
405 I don't remember writing it, but it reads like my prose and I believe
406 I wrote the feature(s) it's describing. So I would have been the
407 likeliest person to write it.
409 Odds are that I did, but I'm not certain.
411 Accordingly, FSF copyright was added.
414 http://lists.gnu.org/archive/html/emacs-devel/2007-02/msg00138.html
415 - briefly removed due to legal uncertainly Jan-Mar 2007. The
416 relevant assignment is under "hp9k800" in copyright.list. File was
417 written by John V. Morris at HP, and disclaimed by the author and
418 HP. So this file is public domain.
422 It was pointed out that K Rodgers only had assigments for VC and
423 ps-print, but had changed several other files. We tried to contact
424 him for a general assignment, but he proved uncommunicative (despite
425 initially indicating to rms he would sign an assignment). As a result, his
426 changes were removed and/or rewritten independently. For details, see
428 http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00225.html
429 http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg00257.html
431 But then an assignment arrived before the release of Emacs 22:
432 http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg01427.html
435 lisp/progmodes/python.el
436 Dave Love alerted us to a potential legal problem:
437 http://lists.gnu.org/archive/html/emacs-pretest-bug/2007-04/msg00459.html
439 On consultation with a lawyer, we found there was no problem:
440 http://lists.gnu.org/archive/html/emacs-devel/2007-05/msg00466.html
443 ** Issues that are "fixed" for the release of Emacs 22, but we may
444 wish to revisit later in more detail
447 admin/check-doc-strings
448 File says it's in the public domain, but that might not make it so.
451 File written long ago by authors with no assignment. Keep them
452 without notices for now, try and contact authors if possible. Be
453 ready to remove these files if the authors ever object.
457 src/acldef.h, chpdef.h, ndir.h
458 On legal advice from Matt Norwood, the following comment was added
459 to these files in Feb/Mar 2007:
461 The code here is forced by the interface, and is not subject to
462 copyright, constituting the only possible expression of the
463 algorithm in this format.
465 With the addition of this notice, these files are OK for the
466 upcoming Emacs-22 release. Post-release, we can revisit this issue
467 and possibly add a list of all authors who have changed these files.
468 (details in email from Matt Norwood to rms, 2007/02/03).
471 Says it was written by Andy Lowry and Joel Spolsky. No entry for
472 either in copyright.list. NB this file is not "constrained" like
473 ms-kermit (rms: "We know it isn't. A comment at the front says it has
474 other bindings which might be handy."). File removed March 2007.
475 Re-add if clear up status at some point.
478 No info on author. File removed March 2007. rms: "It says it is
479 RLK's way of remapping his keyboard, so it is not constrained. I think
480 it was written by RLK. Let's delete it; if we contact RLK again, we
481 can put it back." Actually, RLK == Robert Krawitz has an Emacs
482 assignment. So this could be restored if it is still useful, but Jan Djärv
484 <http://lists.gnu.org/archive/html/emacs-devel/2007-03/msg00673.html>
486 src/m/mips4.h, news-risc.h, pmax.h
487 src/s/aix3-2.h, bsd386.h, hpux8.h, hpux9.h, irix4-0.h, irix5-0.h,
488 netbsd.h, sol2-3.h, usg5-4-2.h
489 - all these (not obviously trivial) files were missing copyrights
490 till Feb 2007, when FSF copyright was added. Matt Norwood advised:
492 For now, I think the best policy is to assume that we do have
493 assignments from the authors (I recall many of these header files
494 as having been originally written by rms), and to attach an FSF
495 copyright with GPL notice. We can amend this if and when we
496 complete the code audit. Any additions to these files by
497 non-assigned authors are arguably "de minimis" contributions to
498 Emacs: small changes or suggestions to a work that are subsumed in
499 the main authors' copyright in the entire work.
501 Here is my (rgm) take on the details of the above files:
504 might be trivial? started trivial, been added to in tiny changes by
505 those with FSF assignment, often result of email suggestions by others.
508 started trivial. Grown by tiny additions, plus chunk
509 from mips.h, which was and is Copyright FSF
512 started trivial. grown in tiny changes, except for maybe Jim Wilson's
516 I would say started non-trivial (1992, rms). only tiny changes since
520 I would say started non-trivial (1993, jimb, heavily based
521 on irix4-0.h). A few borderline non-tiny changes since.
524 started non-trivial, but was heavily based on usg5-4.h, which was and is
525 copyright FSF. only tiny changes since installed.
528 started trivial. only non-tiny change (1994) incorporated code from
529 usg5-4.h, which was and is copyright FSF.
531 aix3-2.h, bsd386.h, hpux8.h, hpux9.h, netbsd.h
532 started trivial, grown in tiny changes.
535 Roland McGrath said to rms (2007/02/17): "I don't really remember
536 anything about it. If I put it in without other comment, then probably
540 Someone might want to tweak the copyright years (for dates before
541 2001) that I used in all these files.
543 Note: erring on the side of caution, I also added notices to some
544 files I thought might be considered non-trivial (if one includes
546 aix4-1.h hpux10.h irix6-0.h irix6-5.h
549 (everything with > 30 non-blank lines, which at least is _some_ kind of
553 *** These are copyright issues that need not be fixed until after
554 Emacs 22 is released (though if they can be fixed before, that is
558 Is it OK to just `cvs remove' a file for legal reasons, or is
559 something more drastic needed? A removed file is still available from
560 CVS, if suitable options are applied. (This CVS issue obviously does
561 not affect a release).
565 Make sure that all files with non-standard copyrights or licenses are
569 REMOVED etc/gnu.xpm, nt/icons/emacs21.ico, nt/icons/sink.ico
570 - Restore if find legal info. emacs21.ico is not due to Davenport.
571 Geoff Voelker checked but could not find a record of where it came
576 Image files from GTK, Gnome are under GPLv2 (no "or later"?). RMS will
577 contact image authors in regards to future switch to v3.
580 etc/TUTORIAL* (translations)
581 switch to GPL (see english TUTORIAL)
582 rms: "We can leave the TUTORIAL translations alone until their
583 maintainers update them."
584 Can adapt short license text from end of GPL translations at:
585 http://www.gnu.org/licenses/translations.html
586 Only a few sentences around the license notice need changing from
591 *** These are copyright issues still to be addressed:
596 ** NOTES ON RELICENSING TO GPL3
598 The EMACS_22_BASE branch was changed to GPLv3 (or later) 2007/07/25.
601 (see http://lists.gnu.org/archive/html/emacs-devel/2007-07/msg01431.html)
603 1. There are some files in Emacs CVS which are not part of Emacs (eg
604 those included from Gnulib). These are all copyright FSF and (at time
605 of writing) GPL >= 2. rms says may as well leave the licenses of these
606 alone (may import them from Gnulib again). These are:
623 Note _not_ included in the above are src/regex.{c,h} (rms: "That
624 forked version is only in Emacs, so definitely relicense that."), and
625 oldXMenu/insque.c (rms: "We wrote that specifically for Emacs, so
626 definitely relicense that.").
628 2. The files that are copyright FSF and AIST, or AIST alone, should be
629 and were updated, ditto the oldXMenu files with FSF copyright, and
630 msdos/is_exec.c and sigaction.c.
634 Files originally in Lucid Widget Library were left alone (excludes
635 ChangeLog, etc), ie remain under GPL v1 or later, or v2 or later.
636 (rms: "We may as well leave this alone, since we are never going to
639 4. There are some files where the FSF holds no copyright. These were
642 leim/MISC-DIC/CTLau-b5.html >= v2
643 leim/MISC-DIC/CTLau.html >= v2
644 (above included in lisp/international/titdic-cnv.el)
645 leim/MISC-DIC/pinyin.map >= v1
646 leim/MISC-DIC/ziranma.cin >= v1
647 leim/SKK-DIC/SKK-JISYO.L >= v2
648 leim/SKK-DIC/README >= v2
649 leim/ja-dic/ja-dic.el >= v2
651 5. At time of writing, some non-Emacs icons included from Gnome remain
652 under GPLv2 (no "or later"). See:
654 etc/images/gnus/README
655 etc/images/mail/README
660 This file is part of GNU Emacs.
662 GNU Emacs is free software: you can redistribute it and/or modify
663 it under the terms of the GNU General Public License as published by
664 the Free Software Foundation, either version 3 of the License, or
665 (at your option) any later version.
667 GNU Emacs is distributed in the hope that it will be useful,
668 but WITHOUT ANY WARRANTY; without even the implied warranty of
669 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
670 GNU General Public License for more details.
672 You should have received a copy of the GNU General Public License
673 along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.