[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gawk-diffs] [SCM] gawk branch, cmake, updated. gawk-4.1.0-733-ga95fcda
|
From: |
Juergen Kahrs |
|
Subject: |
[gawk-diffs] [SCM] gawk branch, cmake, updated. gawk-4.1.0-733-ga95fcda |
|
Date: |
Sun, 24 Aug 2014 14:41:44 +0000 |
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gawk".
The branch, cmake has been updated
via a95fcdabe6db429ece0819ca30702249874a8078 (commit)
from 3cf354e731174233ff2370a8d3cd4cd9ba0b8e91 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://git.sv.gnu.org/cgit/gawk.git/commit/?id=a95fcdabe6db429ece0819ca30702249874a8078
commit a95fcdabe6db429ece0819ca30702249874a8078
Author: Juergen Kahrs <address@hidden>
Date: Sun Aug 24 16:40:39 2014 +0200
New document using-git.texi contains structural outline only.
diff --git a/doc/Makefile.am b/doc/Makefile.am
index 8a0442a..91a7f58 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -24,7 +24,7 @@
## process this file with automake to produce Makefile.in
-info_TEXINFOS = gawk.texi gawkinet.texi
+info_TEXINFOS = gawk.texi gawkinet.texi using-git.texi
man_MANS = gawk.1
@@ -50,7 +50,7 @@ EXTRA_DIST = ChangeLog ChangeLog.0 README.card ad.block
setter.outline \
bc_notes
# Get rid of generated files when cleaning
-CLEANFILES = *.ps *.html *.dvi *~ awkcard.nc awkcard.tr gawk.pdf gawkinet.pdf
awkcard.pdf gawk.1.pdf
+CLEANFILES = *.ps *.html *.dvi *~ awkcard.nc awkcard.tr gawk.pdf gawkinet.pdf
using-git.pdf awkcard.pdf gawk.1.pdf
MAKEINFO = @MAKEINFO@ --no-split --force
@@ -75,9 +75,9 @@ AWKCARD = awkcard.ps
gawk.texi: $(srcdir)/gawktexi.in $(srcdir)/sidebar.awk
awk -f $(srcdir)/sidebar.awk < $(srcdir)/gawktexi.in > gawk.texi
-postscript: gawk.ps gawkinet.ps gawk.1.ps $(AWKCARD)
+postscript: gawk.ps gawkinet.ps using-git.ps gawk.1.ps $(AWKCARD)
-pdf: postscript gawk.pdf gawkinet.pdf awkcard.pdf gawk.1.pdf
+pdf: postscript gawk.pdf gawkinet.pdf using-git.pdf awkcard.pdf gawk.1.pdf
gawk.ps: gawk.dvi
TEXINPUTS=$(srcdir): dvips -o gawk.ps gawk.dvi
@@ -85,6 +85,9 @@ gawk.ps: gawk.dvi
gawkinet.ps: gawkinet.dvi
TEXINPUTS=$(srcdir): dvips -o gawkinet.ps gawkinet.dvi
+using-git.ps: using-git.dvi
+ TEXINPUTS=$(srcdir): dvips -o using-git.ps using-git.dvi
+
gawk.1.ps: gawk.1
-groff -man $(srcdir)/gawk.1 > gawk.1.ps
diff --git a/doc/Makefile.in b/doc/Makefile.in
index d89beff..ba3ee73 100644
--- a/doc/Makefile.in
+++ b/doc/Makefile.in
@@ -164,13 +164,14 @@ AM_V_texidevnull = $(address@hidden@)
am__v_texidevnull_ = $(address@hidden@)
am__v_texidevnull_0 = > /dev/null
am__v_texidevnull_1 =
-INFO_DEPS = $(srcdir)/gawk.info $(srcdir)/gawkinet.info
+INFO_DEPS = $(srcdir)/gawk.info $(srcdir)/gawkinet.info \
+ $(srcdir)/using-git.info
am__TEXINFO_TEX_DIR = $(srcdir)
-DVIS = gawk.dvi gawkinet.dvi
-PDFS = gawk.pdf gawkinet.pdf
-PSS = gawk.ps gawkinet.ps
-HTMLS = gawk.html gawkinet.html
-TEXINFOS = gawk.texi gawkinet.texi
+DVIS = gawk.dvi gawkinet.dvi using-git.dvi
+PDFS = gawk.pdf gawkinet.pdf using-git.pdf
+PSS = gawk.ps gawkinet.ps using-git.ps
+HTMLS = gawk.html gawkinet.html using-git.html
+TEXINFOS = gawk.texi gawkinet.texi using-git.texi
TEXI2DVI = texi2dvi
TEXI2PDF = $(TEXI2DVI) --pdf --batch
MAKEINFOHTML = $(MAKEINFO) --html
@@ -340,7 +341,7 @@ target_alias = @target_alias@
top_build_prefix = @top_build_prefix@
top_builddir = @top_builddir@
top_srcdir = @top_srcdir@
-info_TEXINFOS = gawk.texi gawkinet.texi
+info_TEXINFOS = gawk.texi gawkinet.texi using-git.texi
man_MANS = gawk.1
EXTRA_DIST = ChangeLog ChangeLog.0 README.card ad.block setter.outline \
awkcard.in awkforai.txt texinfo.tex cardfonts \
@@ -365,7 +366,7 @@ EXTRA_DIST = ChangeLog ChangeLog.0 README.card ad.block
setter.outline \
# Get rid of generated files when cleaning
-CLEANFILES = *.ps *.html *.dvi *~ awkcard.nc awkcard.tr gawk.pdf gawkinet.pdf
awkcard.pdf gawk.1.pdf
+CLEANFILES = *.ps *.html *.dvi *~ awkcard.nc awkcard.tr gawk.pdf gawkinet.pdf
using-git.pdf awkcard.pdf gawk.1.pdf
TROFF = groff -t -Tps -U
SEDME = sed -e "s/^level0 restore/level0 restore flashme 100 72 moveto
(Copyright `date '+%m-%d-%y %T'`, FSF, Inc. (all)) show/" \
-e "s/^\/level0 save def/\/level0 save def 30 -48 translate/"
@@ -467,6 +468,10 @@ $(srcdir)/gawkinet.info: gawkinet.texi
gawkinet.dvi: gawkinet.texi
gawkinet.pdf: gawkinet.texi
gawkinet.html: gawkinet.texi
+$(srcdir)/using-git.info: using-git.texi
+using-git.dvi: using-git.texi
+using-git.pdf: using-git.texi
+using-git.html: using-git.texi
.dvi.ps:
$(AM_V_DVIPS)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
$(DVIPS) $(AM_V_texinfo) -o $@ $<
@@ -548,13 +553,16 @@ dist-info: $(INFO_DEPS)
done
mostlyclean-aminfo:
- -rm -rf gawk.t2d gawk.t2p gawkinet.t2d gawkinet.t2p
+ -rm -rf gawk.t2d gawk.t2p gawkinet.t2d gawkinet.t2p using-git.t2d \
+ using-git.t2p
clean-aminfo:
-test -z "gawk.dvi gawk.pdf gawk.ps gawk.html gawkinet.dvi gawkinet.pdf
\
- gawkinet.ps gawkinet.html" \
+ gawkinet.ps gawkinet.html using-git.dvi using-git.pdf \
+ using-git.ps using-git.html" \
|| rm -rf gawk.dvi gawk.pdf gawk.ps gawk.html gawkinet.dvi gawkinet.pdf
\
- gawkinet.ps gawkinet.html
+ gawkinet.ps gawkinet.html using-git.dvi using-git.pdf \
+ using-git.ps using-git.html
maintainer-clean-aminfo:
@list='$(INFO_DEPS)'; for i in $$list; do \
@@ -869,9 +877,9 @@ uninstall-man: uninstall-man1
gawk.texi: $(srcdir)/gawktexi.in $(srcdir)/sidebar.awk
awk -f $(srcdir)/sidebar.awk < $(srcdir)/gawktexi.in > gawk.texi
-postscript: gawk.ps gawkinet.ps gawk.1.ps $(AWKCARD)
+postscript: gawk.ps gawkinet.ps using-git.ps gawk.1.ps $(AWKCARD)
-pdf: postscript gawk.pdf gawkinet.pdf awkcard.pdf gawk.1.pdf
+pdf: postscript gawk.pdf gawkinet.pdf using-git.pdf awkcard.pdf gawk.1.pdf
gawk.ps: gawk.dvi
TEXINPUTS=$(srcdir): dvips -o gawk.ps gawk.dvi
@@ -879,6 +887,9 @@ gawk.ps: gawk.dvi
gawkinet.ps: gawkinet.dvi
TEXINPUTS=$(srcdir): dvips -o gawkinet.ps gawkinet.dvi
+using-git.ps: using-git.dvi
+ TEXINPUTS=$(srcdir): dvips -o using-git.ps using-git.dvi
+
gawk.1.ps: gawk.1
-groff -man $(srcdir)/gawk.1 > gawk.1.ps
diff --git a/doc/using-git.texi b/doc/using-git.texi
new file mode 100644
index 0000000..95a6a5e
--- /dev/null
+++ b/doc/using-git.texi
@@ -0,0 +1,810 @@
+\input texinfo @c -*-texinfo-*-
address@hidden %**start of header (This is for running Texinfo on a region.)
address@hidden using-git.info
address@hidden Workflow in the @command{gawk} project
address@hidden %**end of header (This is for running Texinfo on a region.)
+
address@hidden Network applications
address@hidden
+* Gawkworkflow: (using-git). Workflow in the `gawk' project.
address@hidden direntry
+
address@hidden
address@hidden DOCUMENT book
address@hidden CHAPTER chapter
address@hidden SECTION section
address@hidden DARKCORNER @address@hidden,1cm}, @image{rflashlight,1cm}}
address@hidden iftex
address@hidden
address@hidden DOCUMENT Info file
address@hidden CHAPTER major node
address@hidden SECTION node
address@hidden DARKCORNER (d.c.)
address@hidden ifinfo
address@hidden
address@hidden DOCUMENT web page
address@hidden CHAPTER chapter
address@hidden SECTION section
address@hidden DARKCORNER (d.c.)
address@hidden ifhtml
+
address@hidden FSF
+
address@hidden FN file name
address@hidden FFN File Name
+
address@hidden merge the function and variable indexes into the concept index
address@hidden
address@hidden fn cp
address@hidden vr cp
address@hidden ifinfo
address@hidden
address@hidden fn cp
address@hidden vr cp
address@hidden iftex
+
address@hidden If "finalout" is commented out, the printed output will show
address@hidden black boxes that mark lines that are too long. Thus, it is
address@hidden unwise to comment it out when running a master in case there are
address@hidden overfulls which are deemed okay.
+
address@hidden
address@hidden
address@hidden iftex
+
address@hidden
+
address@hidden Special files are described in chapter 6 Printing Output under
address@hidden 6.7 Special File Names in gawk. I think the networking does not
address@hidden fit into that chapter, thus this separate document. At over 50
address@hidden pages, I think this is the right decision. ADR.
+
address@hidden TITLE Workflow in the @command{gawk} project
address@hidden EDITION 0.0
address@hidden UPDATE-MONTH August, 2014
address@hidden gawk versions:
address@hidden VERSION 4.1
address@hidden PATCHLEVEL 0
+
address@hidden
+This is Edition @value{EDITION} of @address@hidden,
+for the @address@hidden (or later) version of the GNU
+implementation of AWK.
address@hidden 2
+Copyright (C) 2014 Free Software Foundation, Inc.
address@hidden 2
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with the
+Invariant Sections being ``GNU General Public License'', the Front-Cover
+texts being (a) (see below), and with the Back-Cover Texts being (b)
+(see below). A copy of the license is included in the section entitled
+``GNU Free Documentation License''.
+
address@hidden a
address@hidden
+``A GNU Manual''
+
address@hidden
+``You have the freedom to
+copy and modify this GNU manual. Buying copies from the FSF
+supports it in developing GNU and promoting software freedom.''
address@hidden enumerate
address@hidden copying
+
address@hidden
+This file documents the workflow of the developers in the GNU @command{awk}
project.
+
address@hidden
address@hidden ifinfo
+
address@hidden odd
+
address@hidden
address@hidden @value{TITLE}
address@hidden Edition @value{EDITION}
address@hidden @value{UPDATE-MONTH}
address@hidden J@"urgen Kahrs
address@hidden with Arnold D. Robbins
+
address@hidden Include the Distribution inside the titlepage environment so
address@hidden that headings are turned off. Headings on and off do not work.
+
address@hidden
address@hidden 0pt plus 1filll
address@hidden 2
+Published by:
address@hidden 1
+
+Free Software Foundation @*
+51 Franklin Street, Fifth Floor @*
+Boston, MA 02110-1301 USA @*
+Phone: +1-617-542-5942 @*
+Fax: +1-617-542-2652 @*
+Email: @email{gnu@@gnu.org} @*
+URL: @uref{http://www.gnu.org/} @*
+
+ISBN 1-882114-93-0 @*
+
address@hidden
+
address@hidden @sp 2
address@hidden Cover art by ?????.
address@hidden titlepage
+
address@hidden
address@hidden off
address@hidden @thispage@ @ @ @address@hidden @| @|
address@hidden @| @| @address@hidden@ @ @ @thispage
address@hidden iftex
+
address@hidden
address@hidden Top, Preface, (dir), (dir)
address@hidden Introduction
address@hidden node-name, next, previous, up
+
+This file documents the workflow of the developers in the GNU Awk
(@command{gawk})
+version 4.1 and later.
+
address@hidden
address@hidden ifnottex
+
address@hidden
+* Introduction:: About networking.
+* Basics of GIT repositories:: The fundamental environment of the
developer.
+* Conventions used in the repository:: How to behave.
+* Tutorial for a first-time-gawk-contributor:: How to get started with least
pain.
+* FAQs and HOWTOs:: General recipes for daily work.
+* Links:: Where to find the stuff mentioned in this
+ document.
+* GNU Free Documentation License:: The license for this document.
+* Index:: The index.
address@hidden menu
+
address@hidden
+
address@hidden Introduction, Basics of GIT repositories, Top, Top
address@hidden Introduction
+
+This @value{DOCUMENT} is meant to be a description of the working habits
+that were established for collaboration in the GNU Awk project.
+Such stuff tends to become rather dry, and to prevent you from getting
+bored at this early stage, we will begin this @value{CHAPTER} with a
+brief introduction that shows you how to get the
+source code of the GNU Awk project compiled on your machine.
+We do this in order to get you motivated to follow us through the later
+steps that consist mainly of conceptual considerations.
+We hope that (in later, more abstract steps) you will always remember
+this down-to-earth introduction, should you ever wonder what all the
+later bizarre trickery is good for.
+
address@hidden Quick Start: Compiling @command{gawk} in 5 Minutes, Setting up a
proper @command{git} repository, Introduction, Introduction
address@hidden Quick Start: Compiling @command{gawk} in 5 Minutes
+The following steps will look familiar to you, they are not that much
+different from the steps you used in the old days when you downloaded
+a tar ball, extracted it and compiled the source code. It is mainly
+the very first step that looks different; instead of downloading the
+tar ball you need the tool @command{git}.
address@hidden
+ git clone git://git.savannah.gnu.org/gawk.git
+ cd gawk
+ git checkout master
+ ./configure
+ make
+ ./gawk --version
address@hidden example
+The only other difference to your working habits is the third step;
+you have to extract the @emph{master} branch of the current source
+code (there are other branches available, that's the point where
+things get interesting). Isn't this simple ? No, it's not that simple.
+If you plan to go any step further (for example compile the source
+code again next week, including next week's latest update), you will
+need to know what's going on when you use this seemingly simple
address@hidden command (and that's the point where things get bizarre).
+
+In the next @value{CHAPTER} you will find a more thorough conceptual
+explanation, here we are satisfied with getting to know the practical
+steps necessary to get a working environment going that you can use
+in your daily work in a reliable way.
+
+You have created your own repository
+
address@hidden Setting up a proper @command{git} repository, Basics of GIT
repositories, Introduction, Introduction
address@hidden Setting up a proper @command{git} repository
+How can I update and re-build
+
+How can I change to a different branch, what branches are there ?
+
+What is tracking ?
+
address@hidden Basics of GIT repositories, Conventions used in the repository,
Compiling @command{gawk} in 5 minutes, Top
address@hidden Basics of GIT repositories
address@hidden
+* Semantics of Cloning:: What to consider before you clone.
+* Local versus Remote:: Where my source code really is.
+* Tracking and Merging:: What the others are doing.
address@hidden menu
+
address@hidden http://iverilog.wikia.com/wiki/Installation_Guide
address@hidden http://www.linuxjournal.com/article/2840
address@hidden http://git-scm.com/book/en/Git-Branching-Branching-Workflows
address@hidden https://www.atlassian.com/en/git/workflows
address@hidden https://help.github.com/articles/what-is-a-good-git-workflow
address@hidden https://guides.github.com/introduction/flow/index.html
+
address@hidden
+ git config --global user.name "first-name last-name"
+ git config --global user.email address@hidden
+ git config --global color.ui auto
address@hidden smallexample
+
+- How can I use git to contribute source code ?
+You need an account at Savannah. Read this to understand the first steps:
+ http://savannah.gnu.org/maintenance/UsingGit
+ README.git
+Use your account there to register your public ssh key at Savannah.
+Then you are ready to checkout. Remember that (when cloning) you are
+setting up your own local repository and make sure you configure it
+properly.
+ git clone ssh://my_account_name@@git.sv.gnu.org/srv/git/gawk.git
+
address@hidden Semantics of Cloning, Local versus Remote, Introduction,
Introduction
address@hidden Semantics of Cloning
+
address@hidden Local versus Remote, Tracking and Merging, Semantics of Cloning,
Introduction
address@hidden Local versus Remote
+
address@hidden Tracking and Merging, Conventions used in the repository, Local
versus Remote, Introduction
address@hidden Tracking and Merging
+
address@hidden Conventions used in the repository, Tutorial for a
first-time-gawk-contributor, Basics of GIT repositories, Top
address@hidden Conventions used in the repository
address@hidden master
address@hidden stable
address@hidden feature
address@hidden who does what
+
address@hidden Tutorial for a first-time-gawk-contributor, FAQs and HOWTOs,
Conventions used in the repository, Top
address@hidden Tutorial for a first-time-gawk-contributor
+
address@hidden step-by-step instructions for a first-time-gawk-contributor,
step-by-step instructions for a first-time-gawk-administrator, Conventions
used in the repository, Tutorial for a first-time-gawk-contributor
address@hidden step-by-step instructions for a first-time-gawk-contributor
+
address@hidden step-by-step instructions for a first-time-gawk-administrator,
FAQs and HOWTOs, Tutorial for a first-time-gawk-contributor, Tutorial for a
first-time-gawk-contributor
address@hidden step-by-step instructions for a first-time-gawk-administrator
+
address@hidden FAQs and HOWTOs, Links, Tutorial for a
first-time-gawk-contributor, Top
address@hidden FAQs and HOWTOs
address@hidden general recipes for daily work
+
address@hidden Links, GNU Free Documentation License, FAQs and HOWTOs, Top
address@hidden Links
address@hidden references and URLs to books and other texts
+
address@hidden The GNU Free Documentation License.
address@hidden GNU Free Documentation License, Index, Links, Top
address@hidden GNU Free Documentation License
address@hidden FDL (Free Documentation License)
address@hidden Free Documentation License (FDL)
address@hidden GNU Free Documentation License
address@hidden Version 1.3, 3 November 2008
+
address@hidden This file is intended to be included within another document,
address@hidden hence no sectioning command or @node.
+
address@hidden
+Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation,
Inc.
address@hidden://fsf.org/}
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
address@hidden display
+
address@hidden 0
address@hidden
+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.
+
address@hidden
+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
address@hidden without markup, Texinfo input format, address@hidden input
+format, @acronym{SGML} or @acronym{XML} using a publicly available
address@hidden, and standard-conforming simple @acronym{HTML},
+PostScript or @acronym{PDF} designed for human modification. Examples
+of transparent image formats include @acronym{PNG}, @acronym{XCF} and
address@hidden Opaque formats include proprietary formats that can be
+read and edited only by proprietary word processors, @acronym{SGML} or
address@hidden for which the @acronym{DTD} and/or processing tools are
+not generally available, and the machine-generated @acronym{HTML},
+PostScript or @acronym{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.
+
address@hidden
+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.
+
address@hidden
+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.
+
address@hidden
+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:
+
address@hidden A
address@hidden
+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.
+
address@hidden
+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.
+
address@hidden
+State on the Title page the name of the publisher of the
+Modified Version, as the publisher.
+
address@hidden
+Preserve all the copyright notices of the Document.
+
address@hidden
+Add an appropriate copyright notice for your modifications
+adjacent to the other copyright notices.
+
address@hidden
+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.
+
address@hidden
+Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document's license notice.
+
address@hidden
+Include an unaltered copy of this License.
+
address@hidden
+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.
+
address@hidden
+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.
+
address@hidden
+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.
+
address@hidden
+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.
+
address@hidden
+Delete any section Entitled ``Endorsements''. Such a section
+may not be included in the Modified Version.
+
address@hidden
+Do not retitle any existing section to be Entitled ``Endorsements'' or
+to conflict in title with any Invariant Section.
+
address@hidden
+Preserve any Warranty Disclaimers.
address@hidden 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.
+
address@hidden
+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.''
+
address@hidden
+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.
+
address@hidden
+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.
+
address@hidden
+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.
+
address@hidden
+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.
+
address@hidden
+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
address@hidden://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. 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.
+
address@hidden
+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.
+
address@hidden enumerate
+
address@hidden fakenode --- for prepinfo
address@hidden ADDENDUM: How to use this License for your documents
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
address@hidden
address@hidden
+ Copyright (C) @var{year} @var{your name}.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.3
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+ Texts. A copy of the license is included in the section entitled ``GNU
+ Free Documentation License''.
address@hidden group
address@hidden smallexample
+
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the address@hidden'' line with this:
+
address@hidden
address@hidden
+ with the Invariant Sections being @var{list their titles}, with
+ the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
+ being @var{list}.
address@hidden group
address@hidden smallexample
+
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
+
address@hidden Local Variables:
address@hidden ispell-local-pdict: "ispell-dict"
address@hidden End:
+
+
address@hidden Index, , GNU Free Documentation License, Top
address@hidden node-name, next, previous, up
+
address@hidden Index
address@hidden cp
address@hidden
+
+Conventions:
+1. Functions, built-in or otherwise, do NOT have () after them.
+2. Gawk built-in vars and functions are in @code. Also program vars and
+ functions.
+3. HTTP method names are in @code.
+4. Protocols such as echo, ftp, etc are in @samp.
+5. URLs are in @url.
+6. All RFCs in the index. Put a space between `RFC' and the number.
-----------------------------------------------------------------------
Summary of changes:
doc/Makefile.am | 11 +-
doc/Makefile.in | 37 ++-
doc/using-git.texi | 810 ++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 841 insertions(+), 17 deletions(-)
create mode 100644 doc/using-git.texi
hooks/post-receive
--
gawk
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [gawk-diffs] [SCM] gawk branch, cmake, updated. gawk-4.1.0-733-ga95fcda,
Juergen Kahrs <=