More .cvsignore entries?

More .cvsignore entries?

[Kai Großjohann]

When nothing has changed, I get the following in the PCL-CVS buffer:

/----
| In directory .:
| In directory info:
|               Unknown                 info/elisp-covers.texi
|               Unknown                 info/elisp-vol1.texi
|               Unknown                 info/elisp-vol2.texi
| In directory lisp:
|               Modified                lisp/cus-load.el
|               Modified                lisp/finder-inf.el
|               Modified                lisp/loaddefs.el
| In directory man:
|               Unknown                 man/emacs.op
|               Unknown                 man/emacs.ops
\----

I would like to add .cvsignore entries for the "Unknown" files, to
reduce clutter.

Do you mind?

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

Re: More .cvsignore entries?

[Richard Stallman]

elisp-*.texi should exist in lispref, but they should not be in info.
elisp-covers.texi exists in lispref, but emacs-vol*.texi are missing.
(I don't have them in info, either.)

Can you check those two files in, in lispref, so they don't get lost?

emacs.op and emacs.ops are files created in formatting the Emacs
manual.  They should not be in CVS at all.

Re: More .cvsignore entries?

[Robert J. Chassell]

RMS wrote
    
    emacs-vol*.texi are missing.

Those files may have been renamed 

    vol*.texi

some time in the past couple of years to make the name short enough
for some systems.

    emacs/lispref/vol*.texi

exist on my system and they look like what I think we originally
called emacs-vol*.texi.

-- 
    Robert J. Chassell                  bob@rattlesnake.com
    Rattlesnake Enterprises             http://www.rattlesnake.com

Re: More .cvsignore entries?

[Kai Großjohann]

"Robert J. Chassell" <bob@rattlesnake.com> writes:

>     emacs/lispref/vol*.texi
>
> exist on my system and they look like what I think we originally
> called emacs-vol*.texi.

I think this means that somebody should call "cvs remove" on the
files in info/...

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

Re: More .cvsignore entries?

[Stefan Monnier]

> | In directory .:
> | In directory info:
> |               Unknown                 info/elisp-covers.texi
> |               Unknown                 info/elisp-vol1.texi
> |               Unknown                 info/elisp-vol2.texi

Where do they come from ?  Why don't you just delete them ?
If they come back, it's a bug somewhere and we should fix it instead
of hiding the problem by adding them to .cvsignore.
Note that my info/.cvsignore contains just * since all the files
in there are auto-generated (except for the `dir' file, but I also
auto-generate it, even though the result is less good).

> | In directory lisp:
> |               Modified                lisp/cus-load.el
> |               Modified                lisp/finder-inf.el
> |               Modified                lisp/loaddefs.el

These are under CVS so there is no reason to put them in .cvsignore.

> | In directory man:
> |               Unknown                 man/emacs.op
> |               Unknown                 man/emacs.ops

I don't have those here, so maybe it's only generated by some
other version of TeXinfo.  Can you check if that's indeed the case
and if so add *.op and *.ops to the man/.cvsignore file ?


	Stefan

Re: More .cvsignore entries?

[Eli Zaretskii]

On Mon, 15 Jul 2002, Robert J. Chassell wrote:

> RMS wrote
>     
>     emacs-vol*.texi are missing.
> 
> Those files may have been renamed 
> 
>     vol*.texi
> 
> some time in the past couple of years to make the name short enough
> for some systems.

Yes.

>     emacs/lispref/vol*.texi
> 
> exist on my system and they look like what I think we originally
> called emacs-vol*.texi.

Yes.

Re: More .cvsignore entries?

[Kai Großjohann]

"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:

>> | In directory .:
>> | In directory info:
>> |               Unknown                 info/elisp-covers.texi
>> |               Unknown                 info/elisp-vol1.texi
>> |               Unknown                 info/elisp-vol2.texi
>
> Where do they come from ?  Why don't you just delete them ?
> If they come back, it's a bug somewhere and we should fix it instead
> of hiding the problem by adding them to .cvsignore.

I tried to delete them, and "cvs update" put them back.  So I think
it's "cvs remove" time...

(Originally, I thought that they were auto-generated.  That's why I
suggested .cvsignore.)

> Note that my info/.cvsignore contains just * since all the files
> in there are auto-generated (except for the `dir' file, but I also
> auto-generate it, even though the result is less good).
>
>> | In directory lisp:
>> |               Modified                lisp/cus-load.el
>> |               Modified                lisp/finder-inf.el
>> |               Modified                lisp/loaddefs.el
>
> These are under CVS so there is no reason to put them in .cvsignore.

Right.  It's because of "make bootstrap", I know.

>> | In directory man:
>> |               Unknown                 man/emacs.op
>> |               Unknown                 man/emacs.ops
>
> I don't have those here, so maybe it's only generated by some
> other version of TeXinfo.  Can you check if that's indeed the case
> and if so add *.op and *.ops to the man/.cvsignore file ?

Done.

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

Re: More .cvsignore entries?

[Stefan Monnier]

> >> | In directory .:
> >> | In directory info:
> >> |               Unknown                 info/elisp-covers.texi
> >> |               Unknown                 info/elisp-vol1.texi
> >> |               Unknown                 info/elisp-vol2.texi
> >
> > Where do they come from ?  Why don't you just delete them ?
> > If they come back, it's a bug somewhere and we should fix it instead
> > of hiding the problem by adding them to .cvsignore.
> 
> I tried to delete them, and "cvs update" put them back.  So I think
> it's "cvs remove" time...

How on earth could `cvs update' put them back and at the same time
have `cvs -n update' say that they are "Unknown" ?
I doubt `cvs remove' will help, but feel free to try.
As far as I can see, there is simply no such info/elisp-covers.texi
file in the repository at all.

BTW, I'm mildly annoyed at the use of @copying since my texinfo
burps on it saying it's an unknown command.  I'm using texinfo-4.1
from RedHat-7.3 which is not ancient in my book.
Until now, texinfo-4.0 was enough.  Is @copying really important ?


	Stefan

Re: More .cvsignore entries?

[Eli Zaretskii]

On Mon, 15 Jul 2002, Stefan Monnier wrote:

> BTW, I'm mildly annoyed at the use of @copying since my texinfo
> burps on it saying it's an unknown command.  I'm using texinfo-4.1
> from RedHat-7.3 which is not ancient in my book.
> Until now, texinfo-4.0 was enough.

FWIW, I agree: it's not a good idea to require the latest Texinfo so 
close to its release (although the CVS version is supposed to be ``not 
for the faint of heart'').  I'd suggest to wait for at least the next 
release, or for several more months, whichever comes first.

> Is @copying really important ?

I guess it's important for Richard, since he asked for that feature.  
AFAIK, its importance is that it guarantees the copying conditions are 
output in all formats supported by makeinfo, especially HTML (where until 
now there was no copyright notice at all).

Re: More .cvsignore entries?

[Robert J. Chassell]

   > BTW, I'm mildly annoyed at the use of @copying ...
   > Is @copying really important ?

Yes, it is important.

It turned out that documents in various output types, in particular
HTML, were being published *without* any copyright or permissions
notice.  People forgot to put them in.

This meant that people were forbidden to copy, much less modify, much
GNU documentation except for fair use.

This failure was inadvertent:  the people who wrote documentation --
just about everyone who wrote documentation -- provided copying
notices for the `older' cases, for Texinfo itself, for Info, and for
DVI (and deriviatives such as PDF); but they simply forgot HTML!

The @copying command and its companion, @insertcopying,
enable everyone to insert proper copying text.

Here is a sample template that illustrates the use of @copying and
@insertcopying.  It also illustrates, I hope, a proper *verbatim*
license.

(There is some continued discussion concerning the wording of a
verbatim license; for example, it probably does not matter whether you
include the phrase `without royalty' -- the GNU Web site does not:

    http://www.gnu.org/licenses/licenses.html#VerbatimCopying

but the license is more clear if you do include the phrase.)

(For modifiable works, please use the GNU Free Documentation License.
It was cleverly crafted to mean the same ordinary people, lawyers, and
judges, and to be acceptable to many hard copy publishers as well as
to people who favor freedom.)

Also, this template includes 6 different shell commands for formatting
the file.  It includes XML and DocBook output.

I put these commands into an @ignore ... @end ignore section near the
beginning of the file.  These commands are very useful.  (Since I
mostly work in an X windowing system, I simply copy them from the
Emacs window in which I am editing the Texinfo file into an xterm and
run them.)

I urge you to edit your Texinfo file in GNU Emacs using Texinfo mode.
The mode simplifies your work.  For example, I use the `C-u C-c C-u
C-a' (texinfo-all-menus-update) command all the time.  I never update
node pointers or write menus myself.

Best wishes

--
    Robert J. Chassell                  bob@rattlesnake.com
    Rattlesnake Enterprises             http://www.rattlesnake.com


Here is the sample template:



\input texinfo.tex                         @c -*-texinfo-*-
@comment %**start of header
@setfilename test.info
@settitle Texinfo Test
@smallbook
@comment %**end of header

@ignore
 ## Summary of shell commands to create various output formats:

    ## Info output
    makeinfo --force --fill-column=70 --no-split --paragraph-indent=0 \
    --verbose test.texi

    ## DVI output
    texi2dvi test.texi

    ## Plain text output
    makeinfo --fill-column=70 --no-split --paragraph-indent=0 \
    --verbose --no-headers --output=test.txt  \
    test.texi

    ## HTML output
    makeinfo --no-split --html test.texi

    ## DocBook output
    makeinfo --docbook --no-split --paragraph-indent=0 \
    --verbose test.texi

    ## XML output
    makeinfo --xml --no-split --paragraph-indent=0 \
    --verbose test.texi

@end ignore

@copying
Copyright @copyright{} 2002 Robert J. Chassell

This is a test document.

@quotation
Permission is granted to make and distribute verbatim copies
of this entire document without royalty provided the
copyright notice and this permission notice are preserved on
all copies.

@c    The remainder of this paragraph applies to and should
@c    appear in the Texinfo source.
@c Permission is granted to process this file through TeX or
@c other converter and publish the results, provided the
@c published document carries a copying permission notice
@c identical to this one except for the removal of this
@c paragraph (this paragraph not being relevant to the
@c published document).

Permission is granted to copy and distribute translations
of this document into another language, except that this
permission notice may be stated in a translation approved
by the Free Software Foundation.
@end quotation
@end copying

@c For smallbook format, use smaller than normal amounts of
@c whitespace between chapters, sections, and paragraphs.
@c Remember to comment this out if you are not using smallbook format!
@tex
\global\chapheadingskip = 15pt plus 4pt minus 2pt
\global\secheadingskip = 12pt plus 3pt minus 2pt
\global\subsecheadingskip = 9pt plus 2pt minus 2pt \global\parskip 2pt plus 1pt
@end tex

@titlepage
@sp 6
@center @titlefont{Test document}
@sp 4
@center by Robert J. Chassell

@page
@vskip 0pt plus 1filll
@insertcopying
@end titlepage

@contents

@ifnottex
@node Top, Chapter One, (dir), (dir)
@top Test Top
@insertcopying
@end ifnottex

@menu
* Chapter One::
* Chapter Two::
@end menu

@node Chapter One, Chapter Two, Top, Top
@comment node, next, prev, up
@chapter Chapter One

Contents of chapter 1.

The quick brown fox jumps over the lazy dog.

The quick brown fox jumps over the lazy dog.

Here is an bulleted list:

@itemize @bullet

@item
First item.

@item
Second item.
@end itemize

@node Chapter Two,  , Chapter One, Top
@chapter Chapter Two

Contents of chapter 2
@cindex bar

The lazy dog opened an eye.

@menu
* Section TwoA::
* Section TwoB::
@end menu

@node Section TwoA, Section TwoB, Chapter Two, Chapter Two
@section SectionTwoA

Contents of Section 2A

The quick brown fox jumps over the lazy dog.

@smallexample
(+ 2 2)
@end smallexample

@node Section TwoB,  , Section TwoA, Chapter Two
@section Section TwoB

Contents of Section 2B

The lazy dog jumps over the quick brown fox.

@bye

Re: More .cvsignore entries?

[Kai Großjohann]

"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:

> BTW, I'm mildly annoyed at the use of @copying since my texinfo
> burps on it saying it's an unknown command.  I'm using texinfo-4.1
> from RedHat-7.3 which is not ancient in my book.
> Until now, texinfo-4.0 was enough.  Is @copying really important ?

Does this mean I should change man/tramp.texi?  Sure I can do that.
Since I'm lazy: where could I copy-and-paste the copying stuff?

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

Template for GFDL copying

[Robert J. Chassell]

   Does this mean I should change man/tramp.texi?  Sure I can do that.
   Since I'm lazy: where could I copy-and-paste the copying stuff?

Here is a template that I hope provides the right material.  I just
realized that I have to change some of my files, too.  For some
reason, I thought I had made the changes, but had not.... :-(

Incidentally, we put the actual license itself inside an @quotation
... @end quotation environment in side of @copying because it looks
better that way.

Please note that you need to include the GNU Free Documentation
License as an appendix to your document.  One is included here.

Also, this requires Texinfo 4.2.

\input texinfo.tex   @c -*-texinfo-*-
@comment %**start of header
@setfilename copying-gfdl.info
@settitle Template for GFDL copying
@smallbook
@comment %**end of header

@c Template for GFDL copying: note that the GFDL in an appendix
@c contains a copying licence that is within @display ... @end display
@c and does not need changing.

@ignore
 ## Summary of shell commands to create various output formats:

    ## Info output
    makeinfo --force --fill-column=70 --no-split --paragraph-indent=0 \
    --verbose copying-gfdl.texi

    ## DVI output
    texi2dvi copying-gfdl.texi

    ## Plain text output
    makeinfo --fill-column=70 --no-split --paragraph-indent=0 \
    --verbose --no-headers --output=copying-gfdl.txt  \
    copying-gfdl.texi

    ## HTML output
    makeinfo --no-split --html copying-gfdl.texi

    ## DocBook output
    makeinfo --docbook --no-split --paragraph-indent=0 \
    --verbose copying-gfdl.texi

    ## XML output
    makeinfo --xml --no-split --paragraph-indent=0 \
    --verbose copying-gfdl.texi

@end ignore

@copying
Copyright @copyright{} 1990, 1991, 1992, 1993, 1994, 1995, 1997, 2001, 2002 Free Software Foundation, Inc.

@c <<An explanation of the document goes here>>

@c Perhaps include the following:
@ignore
Published by the Free Software Foundation, Inc.@*
59 Temple Place, Suite 330@*
Boston, MA 02111-1307 USA@*

Edition @value{edition-number}, @value{update-date}

@c Printed copies are available for $ZZ each.@*
ISBN 1-882114-YY-Y
@end ignore

@quotation
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
any later version published by the Free Software Foundation; there
being no Invariant Section, with the Front-Cover Texts being ``A GNU
Manual'', and with the Back-Cover Texts as in (a) below.  A copy of
the license is included in the section entitled ``GNU Free
Documentation License''.
@end quotation

@quotation
(a) The FSF's Back-Cover Text is: ``You have freedom to copy and
modify this GNU Manual, like GNU software.  Copies published by the
Free Software Foundation raise funds for GNU development.''
@end quotation
@end copying

@c For smallbook format, use smaller than normal amounts of
@c whitespace between chapters, sections, and paragraphs.
@c Remember to comment this out if you are not using smallbook format!
@tex
\global\chapheadingskip = 15pt plus 4pt minus 2pt
\global\secheadingskip = 12pt plus 3pt minus 2pt
\global\subsecheadingskip = 9pt plus 2pt minus 2pt \global\parskip 2pt plus 1pt
@end tex

@titlepage
@sp 6
@center @titlefont{Template for GFDL copying}
@sp 4
@center by Robert J. Chassell

@page
@vskip 0pt plus 1filll
@insertcopying
@end titlepage

@contents

@ifnottex
@node Top, Chapter One, (dir), (dir)
@top Template for GFDL copying
@insertcopying
@end ifnottex

@menu
* Chapter One::                 
* GNU Free Documentation License::  
@end menu

@node Chapter One, GNU Free Documentation License, Top, Top
@comment node, next, prev, up
@chapter Chapter One

The Texinfo source for this document contains a template for GFDL
copying: note that GFDL in appendix contains a copying licence that is
within @code{@@display} ... @code{@@end display} and does not need
changing.

@node GNU Free Documentation License,  , Chapter One, Top
@appendix GNU Free Documentation License

@cindex FDL, GNU Free Documentation License
@center Version 1.1, March 2000

@display
Copyright @copyright{} 2000 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA  02111-1307, USA

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
written 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 that contains a
notice placed by the copyright holder saying it can be distributed
under the terms of this License.  The ``Document'', below, refers to any
such manual or work.  Any member of the public is a licensee, and is
addressed as ``you''.

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.  (For example, 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.

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 ``Transparent'' copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, whose contents can be viewed and edited directly and
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 has been designed to thwart or discourage
subsequent modification by readers is not Transparent.  A copy that is
not ``Transparent'' is called ``Opaque''.

Examples of suitable formats for Transparent copies include plain
@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
@acronym{SGML} or @acronym{XML} using a publicly available
@acronym{DTD}, and standard-conforming simple @acronym{HTML} designed
for human modification.  Opaque formats include PostScript,
@acronym{PDF}, proprietary formats that can be read and edited only by
proprietary word processors, @acronym{SGML} or @acronym{XML} for which
the @acronym{DTD} and/or processing tools are not generally available,
and the machine-generated @acronym{HTML} 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.

@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 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 publicly-accessible computer-network location containing a complete
Transparent copy of the Document, free of added material, which the
general network-using public has access to download anonymously at no
charge using public-standard network protocols.  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 less than five).

@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'', and 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
In any section entitled ``Acknowledgments'' or ``Dedications'',
preserve the section's title, and preserve in the section all the
substance and tone of each of the contributor acknowledgments
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 as ``Endorsements''
or to conflict in title with any Invariant Section.
@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.

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 ``Acknowledgments'',
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, does not as a whole count as a Modified Version
of the Document, provided no compilation copyright is claimed for the
compilation.  Such a compilation is called an ``aggregate'', and this
License does not apply to the other self-contained works thus compiled
with the Document, on account of their being thus compiled, if they
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 quarter
of the entire aggregate, the Document's Cover Texts may be placed on
covers that surround only the Document within the aggregate.
Otherwise they must appear on covers around 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 provided that you also include the
original English version of this License.  In case of a disagreement
between the translation and the original English version of this
License, the original English version will prevail.

@item
TERMINATION

You may not copy, modify, sublicense, or distribute the Document except
as expressly provided for under this License.  Any other attempt to
copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License.  However,
parties who have received copies, or rights, from you under this
License will not have their licenses terminated so long as such
parties remain in full compliance.

@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{http://www.gnu.org/copyleft/}.

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.
@end enumerate


@bye





@ignore

To:  
Subject: sample Texinfo file template 
Reply-to: bob@rattlesnake.com 
--text follows this line-- 

Here is a template for a Texinfo file; do please write your
documentation using Texinfo.  It works very well.

This template uses the new @copying and @insertcopying commands.
These new commands simplify inserting permissions and mean that
copying statements now appear in all the different output formats.
(Previously, just about everyone forgot HTML!)

The one disadvantage of these new commands is that you need the new
Texinfo version 4.2 to run them, but this new version is pretty good,
so you might has well get it.

This sample template also illustrates, I hope, a proper *verbatim*
license.

(Incidentally, there is some continued discussion concerning the
wording of a verbatim license; for example, it probably does not
matter whether you include the phrase `without royalty' -- the 
GNU Web site does not:

    http://www.gnu.org/licenses/licenses.html#VerbatimCopying

but the license is more clear if you do include the phrase.)

(For modifiable works, please use the GNU Free Documentation License.
It was cleverly crafted to mean the same ordinary people, lawyers, and
judges, and to be acceptable to many hard copy publishers as well as
to people who favor freedom.)

Also, this template includes 6 different shell commands for formatting
the file.  It includes XML and DocBook output.

I put these commands into an @ignore ... @end ignore section near the
beginning of the file.  These commands are very useful.  (Since I
mostly work in an X windowing system, I simply copy them from the
Emacs window in which I am editing the Texinfo file into an xterm and
run them.)

I urge you to edit your Texinfo file in GNU Emacs using Texinfo mode.
The mode simplifies your work.  For example, I use the `C-u C-c C-u
C-a' (texinfo-all-menus-update) command all the time.  I never update
node pointers or write menus myself.

Best wishes

--
    Robert J. Chassell                  bob@rattlesnake.com
    Rattlesnake Enterprises             http://www.rattlesnake.com


Here is the sample template:

@end ignore

Re: More .cvsignore entries?

[Eli Zaretskii]

On Tue, 16 Jul 2002 Kai.Grossjohann@CS.Uni-Dortmund.DE wrote:

> Since I'm lazy: where could I copy-and-paste the copying stuff?

emacs.texi should have what you want, with the caveat about the HTML 
version and copying conditions; see the other message in this thread.

Re: More .cvsignore entries?

[Richard Stallman]

    Those files may have been renamed 

	vol*.texi

I see.  Yes, I have those too.