Browse Source

* doc/fdl.texi: New.

* doc/dejagnu.texi (Variable Index): New.
	Add more concept index entries.
	(GNU Free Documentation License): New appendix.
psql
Ben Elliston 8 years ago
parent
commit
54c113a249
  1. 7
      ChangeLog
  2. 57
      doc/dejagnu.texi
  3. 466
      doc/fdl.texi

7
ChangeLog

@ -1,3 +1,10 @@
2018-12-02 Ben Elliston <bje@gnu.org>
* doc/fdl.texi: New.
* doc/dejagnu.texi (Variable Index): New.
Add more concept index entries.
(GNU Free Documentation License): New appendix.
2018-12-02 Ben Elliston <bje@gnu.org>
* doc/dejagnu.texi (Procedure Index): New. Add Texinfo function

57
doc/dejagnu.texi

@ -54,8 +54,10 @@ Free Documentation License''.
* Extending DejaGnu::
* Unit testing::
* Reference::
* GNU Free Documentation License::
* Concept Index::
* Procedure Index::
* Variable Index::
@detailmenu
@ -231,6 +233,7 @@ The user-visible utility procedure @code{unsetenv} is
@node Design goals, A POSIX Conforming Test Framework, Release Notes, Introduction
@section Design goals
@cindex design goals
DejaGnu grew out of the internal needs of Cygnus Solutions (formerly
Cygnus Support). Cygnus maintained and enhanced a variety of free
@ -275,8 +278,9 @@ it. Currently DejaGnu can use @code{ssh}, @code{rsh}, @code{rlogin},
@node A POSIX Conforming Test Framework, Installation, Design goals, Introduction
@section A POSIX compliant test framework
@cindex POSIX compliant test framework
@cindex POSIX 1003.3
DejaGnu conforms to the POSIX 1003.3 standard for test frameworks. Rob
Savoye was a member of that committee.
@ -549,6 +553,7 @@ An informational message about the test case.
@node Invoking runtest, Common Operations, Output States, Runtest
@subsection Invoking runtest
@cindex runtest, invoking
This is the full set of command line options that @code{runtest}
recognizes. Option names may be abbreviated to the shortest unique
@ -746,6 +751,7 @@ DejaGnu @emph{Makefile}; their values are captured in the
@node Common Operations, , Invoking runtest, Runtest
@subsection Common Options
@cindex options, common
Typically, you don't need to use any command line options. The
@code{--tool} option is only required when there is more than one
@ -788,7 +794,6 @@ a more detailed explanation of each @code{runtest} option.
@node Output Files, , Runtest, Running tests
@section Output files
@cindex output files
DejaGnu always writes two kinds of output files. Summary output is
written to the @file{.sum} file, and detailed output is written to the
@ -806,6 +811,7 @@ available. Each of these will be described in turn.
@node Summary log file, Detailed log file, , Output Files
@subsection Summary log file
@cindex output file, summary log
DejaGnu always produces a summary (@file{.sum}) output file. This
summary lists the names of all test files run. For each test file, one
@ -855,6 +861,7 @@ option to select a different output directory.
@node Detailed log file, Debug log file, Summary log file, Output Files
@subsection Detailed log file
@cindex output file, detailed log
DejaGnu also saves a detailed log file (@file{.log}), showing any output
generated by test cases as well as the summary output. For example,
@ -902,6 +909,7 @@ a different output directory.
@node Debug log file, , Detailed log file, Output Files
@subsection Debug log file
@cindex output file, debug log
The @code{runtest} option @code{--debug} creates a file showing the
output from Expect in debugging mode. The @file{dbg.log} file is created
@ -996,6 +1004,7 @@ make the actions for fail-safe patterns produce messages starting with
@node Customizing DejaGnu, Extending DejaGnu, Running tests, Top
@chapter Customizing DejaGnu
@cindex customization
The site configuration file, @file{site.exp}, captures
configuration-dependent values and propagates them to the DejaGnu test
@ -1048,6 +1057,7 @@ command line.
@node Global config file, Local config file, , Customizing DejaGnu
@section Global config file
@cindex configuration file, global
The global configuration file is where all the target specific
configuration variables for a site are set. For example, a centralized
@ -1108,6 +1118,7 @@ compiler testing.
@node Local config file, Board config file, Global config file, Customizing DejaGnu
@section Local config file
@cindex configuration file, local
It is usually more convenient to keep these @emph{manual overrides} in
the @file{site.exp} local to each test directory, rather than in the
@ -1182,6 +1193,7 @@ test cases, the CXXFLAGS and LDFLAGS are supplied by DejaGnu itself for
cross testing, but to test a compiler, GCC needs to manipulate these
itself.
@vindex test_timeout
The local @file{site.exp} may also set Tcl variables such as
@code{test_timeout} which can control the amount of time (in seconds) to
wait for a remote test to complete. If not specified,
@ -1189,6 +1201,7 @@ wait for a remote test to complete. If not specified,
@node Board config file, Remote host testing, Local config file, Customizing DejaGnu
@section Board configuration file
@cindex configuration file, board
The board configuration file is where board-specific configuration
details are stored. A board configuration file contains all the
@ -1272,6 +1285,7 @@ library for embedded systems comprising of non-GPL'd code
@node Remote host testing, Config file values, Board config file, Customizing DejaGnu
@section Remote host testing
@cindex testing on remote hosts
DejaGnu also supports running the tests on a remote host. To set this
up, the remote host needs an FTP server, and a telnet server. Currently
@ -1380,7 +1394,9 @@ your local configuration. The -v's are optional.
@node Config file values, , Remote host testing, Customizing DejaGnu
@section Config file values
@cindex configuration values
@vindex target_info
DejaGnu uses a Tcl associative array to hold all the info for each
machine. In the case of a Canadian cross, this means host information as
well as target information. The named array is called
@ -1507,6 +1523,8 @@ as rsh is mostly used to test Unix machines within a local network.
@node Extending DejaGnu, Unit testing, Customizing DejaGnu, Top
@chapter Extending DejaGnu
@cindex extensions
@cindex extending DejaGnu
@menu
* Adding a new testsuite::
@ -1522,6 +1540,7 @@ as rsh is mostly used to test Unix machines within a local network.
@node Adding a new testsuite, Adding a new tool, , Extending DejaGnu
@section Adding a new testsuite
@cindex adding, testsuite
The testsuite for a new tool should always be located in that tools
source directory. DejaGnu require the directory be named
@ -1704,6 +1723,7 @@ also write a real version routine soon.
@node Adding a new target, Adding a new board, Adding a new tool, Extending DejaGnu
@section Adding a new target
@cindex adding, target
DejaGnu has some additional requirements for target support, beyond the
general-purpose provisions of a @code{configure} script. DejaGnu must
@ -1739,6 +1759,7 @@ connected.
@node Adding a new board, Board file values, Adding a new target, Extending DejaGnu
@section Adding a new board
@cindex adding, board
Adding a new board consists of creating a new board configuration
file. Examples are in @file{dejagnu/baseboards}. Usually to make a new
@ -1983,7 +2004,8 @@ existing GDB tests, for reporting purposes. Thereafter, new GDB tests
built up a family of Tcl procedures specialized for GDB testing.
@subsection Hints on writing a test case
@cindex Hints on writing a test case
@cindex hints on writing a test case
@cindex test cases, writing
It is safest to write patterns that match all the output generated by
the tested program; this is called closure. If a pattern does not match
@ -2035,6 +2057,7 @@ procedures @code{error} or @code{warning}.
@node Debugging a test case, Adding a test case to a testsuite, Writing a test case, Extending DejaGnu
@section Debugging a test case
@cindex test cases, debugging
These are the kinds of debugging information available from DejaGnu:
@ -2081,6 +2104,7 @@ file and, if @code{--debug} is given, to @file{dbg.log}.
@node Adding a test case to a testsuite, Test case variables, Debugging a test case, Extending DejaGnu
@section Adding a test case to a testsuite
@cindex test cases, adding
There are two slightly different ways to add a test case. One is to add
the test case to an existing directory. The other is to create a new
@ -2117,28 +2141,34 @@ changed.
@table @code
@item $prms_id
@vindex prms_id
The bug tracking system (eg. PRMS/GNATS) number identifying a
corresponding bug report (@emph{0} if you do not specify it).
@item $bug_id
@vindex bug_id
An optional bug ID, perhaps a bug identification number from another
organization (@emph{0} if you do not specify it).
@item $subdir
@vindex subdir
The subdirectory for the current test case.
@item $exec_output
@vindex exec_output
This is the output from a @code{$@{tool@}_load} command. This only
applies to tools like GCC and GAS which produce an object file that must
in turn be executed to complete a test.
@item $comp_output
@vindex comp_output
This is the output from a @code{$@{tool@}_start} command. This is
conventionally used for batch-oriented programs, like GCC and GAS, that
may produce interesting output (warnings, errors) without further
interaction.
@item $expect_out(buffer)
@vindex expect_out(buffer)
The output from the last command. This is an internal variable set by
Expect. More information can be found in the Expect manual.
@end table
@ -2155,7 +2185,7 @@ Expect. More information can be found in the Expect manual.
@node What is unit testing?, The dejagnu_h header file, , Unit testing
@section What is unit testing?
@cindex Unit testing
@cindex unit testing
Most regression testing as done by DejaGnu is system testing: the
complete application is tested all at once. Unit testing is for testing
@ -2171,6 +2201,7 @@ the testcase can also function as a compliance test.
@node The dejagnu_h header file, C unit testing API, What is unit testing?, Unit testing
@section The dejagnu.h header file
@cindex dejagnu.h header
DejaGnu uses a single header file, @file{dejagnu.h} to assist in unit
testing. As this file also produces its one test state output, it can be
@ -2183,6 +2214,7 @@ the output messages, and then merge them into DejaGnu's.
@node C unit testing API, C++ unit testing API, The dejagnu_h header file, Unit testing
@section C unit testing API
@cindex C unit testing API
All of the functions that take a @code{msg} parameter use a C @code{char
*} that is the message to be displayed. There currently is no support
@ -2232,6 +2264,7 @@ outputs.
@node C++ unit testing API, , C unit testing API, Unit testing
@section C++ unit testing API
@cindex C++ unit testing API
All of the methods that take a @code{msg} parameter use a C char * or
STL string, that is the message to be displayed. There currently is no
@ -2278,8 +2311,8 @@ outputs.
@end itemize
@node Reference, , Unit testing, Top
@chapter Reference
@node Reference, GNU Free Documentation License, Unit testing, Top
@appendix Framework reference
@menu
* Builtin Procedures::
@ -5392,14 +5425,22 @@ This makes runtest exit. It is abbreviated as @emph{q}.
@item @code{}
@end table
@node Concept Index
@node GNU Free Documentation License, Reference, Concept Index, Top
@appendix GNU Free Documentation License
@include fdl.texi
@node Concept Index, GNU Free Documentation License, Procedure Index, Top
@unnumbered Concept Index
@printindex cp
@node Procedure Index
@node Procedure Index, Concept Index, Variable Index, Top
@unnumbered Procedure Index
@printindex fn
@node Variable Index, Procedure Index, , Top
@unnumbered Variable Index
@printindex vr
@bye
@c LocalWords: subdirectory

466
doc/fdl.texi

@ -0,0 +1,466 @@
@c The GNU Free Documentation License.
@center Version 1.3, 3 November 2008
@c This file is intended to be included within another document,
@c hence no sectioning command or @node.
@display
Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
@uref{https://fsf.org/}
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@end display
@enumerate 0
@item
PREAMBLE
The purpose of this License is to make a manual, textbook, or other
functional and useful document @dfn{free} in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
This License is a kind of ``copyleft'', which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
@item
APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The ``Document'', below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as ``you''. You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
A ``Modified Version'' of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A ``Secondary Section'' is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
any mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
The ``Invariant Sections'' are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
The ``Cover Texts'' are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
A ``Transparent'' copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not ``Transparent'' is called ``Opaque''.
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, La@TeX{} input
format, SGML or XML using a publicly available
DTD, and standard-conforming simple HTML,
PostScript or PDF designed for human modification. Examples
of transparent image formats include PNG, XCF and
JPG@. Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, SGML or
XML for which the DTD and/or processing tools are
not generally available, and the machine-generated HTML,
PostScript or PDF produced by some word processors for
output purposes only.
The ``Title Page'' means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, ``Title Page'' means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.
The ``publisher'' means any person or entity that distributes copies
of the Document to the public.
A section ``Entitled XYZ'' means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as ``Acknowledgements'',
``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the Title''
of such a section when you modify the Document means that it remains a
section ``Entitled XYZ'' according to this definition.
The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
@item
VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
@item
COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
@item
MODIFICATIONS
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
@enumerate A
@item
Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
@item
List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
@item
State on the Title page the name of the publisher of the
Modified Version, as the publisher.
@item
Preserve all the copyright notices of the Document.
@item
Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
@item
Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
@item
Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
@item
Include an unaltered copy of this License.
@item
Preserve the section Entitled ``History'', Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled ``History'' in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
@item
Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the ``History'' section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
@item
For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
@item
Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
@item
Delete any section Entitled ``Endorsements''. Such a section
may not be included in the Modified Version.
@item
Do not retitle any existing section to be Entitled ``Endorsements'' or
to conflict in title with any Invariant Section.
@item
Preserve any Warranty Disclaimers.
@end enumerate
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.
You may add a section Entitled ``Endorsements'', provided it contains
nothing but endorsements of your Modified Version by various
parties---for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
@item
COMBINING DOCUMENTS
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled ``History''
in the various original documents, forming one section Entitled
``History''; likewise combine any sections Entitled ``Acknowledgements'',
and any sections Entitled ``Dedications''. You must delete all
sections Entitled ``Endorsements.''
@item
COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
@item
AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an ``aggregate'' if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
@item
TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
If a section in the Document is Entitled ``Acknowledgements'',
``Dedications'', or ``History'', the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.
@item
TERMINATION
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
@item
FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
@uref{https://www.gnu.org/licenses/}.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License ``or any later version'' applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation. If the Document
specifies that a proxy can decide which future versions of this
License can be used, that proxy's public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
@item
RELICENSING
``Massive Multiauthor Collaboration Site'' (or ``MMC Site'') means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server. A
``Massive Multiauthor Collaboration'' (or ``MMC'') contained in the
site means any set of copyrightable works thus published on the MMC
site.
``CC-BY-SA'' means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
``Incorporate'' means to publish or republish a Document, in whole or
in part, as part of another Document.
An MMC is ``eligible for relicensing'' if it is licensed under this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole
or in part into the MMC, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
@end enumerate
@c Local Variables:
@c ispell-local-pdict: "ispell-dict"
@c End:
Loading…
Cancel
Save