gawk-diffs
[Top][All Lists]
Advanced

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

[gawk-diffs] [SCM] gawk branch, gawk-4.2-stable, updated. gawk-4.1.0-306


From: Arnold Robbins
Subject: [gawk-diffs] [SCM] gawk branch, gawk-4.2-stable, updated. gawk-4.1.0-3064-g35855fa
Date: Sat, 27 Oct 2018 14:50:34 -0400 (EDT)

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, gawk-4.2-stable has been updated
       via  35855fa516205a3cb302567616915a3ec6fd9c61 (commit)
      from  c5fed09ab5c3b94643498bef7b62c8d58f177114 (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=35855fa516205a3cb302567616915a3ec6fd9c61

commit 35855fa516205a3cb302567616915a3ec6fd9c61
Author: Arnold D. Robbins <address@hidden>
Date:   Sat Oct 27 21:50:00 2018 +0300

    Doc update: don't post bug reports in web forums.

diff --git a/doc/ChangeLog b/doc/ChangeLog
index a2f0166..5c5e149 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,8 @@
+2018-10-27         Arnold D. Robbins     <address@hidden>
+
+       * gawktexi.in (Usenet): Mention that web forums are also not
+       the right place for gawk bug reports.
+
 2018-10-23         Arnold D. Robbins     <address@hidden>
 
        * gawktexi.in (Bug address): Mention the GNU Kind
diff --git a/doc/gawk.info b/doc/gawk.info
index e4bee7c..b18d965 100644
--- a/doc/gawk.info
+++ b/doc/gawk.info
@@ -29817,8 +29817,13 @@ B.4.2 Please Don't Post Bug Reports to USENET
 Usenet/Internet newsgroup 'comp.lang.awk'.  Although some of the 'gawk'
 developers occasionally read this news group, the primary 'gawk'
 maintainer no longer does.  Thus it's virtually guaranteed that he will
-_not_ see your posting.  The steps described here are the only
-officially recognized way for reporting bugs.  Really.
+_not_ see your posting.
+
+   Similarly, posting bug reports or questions in web forums, such as
+Stack Overflow (https://stackoverflow.com/) may get you an answser, but
+it won't be from the 'gawk' maintainers, who do not spend their time in
+web forums.  The steps described here are the only officially recognized
+way for reporting bugs.  Really.
 
 
 File: gawk.info,  Node: Maintainers,  Prev: Usenet,  Up: Bugs
@@ -36655,38 +36660,38 @@ Node: VMS Old Gawk1198853
 Node: Bugs1199324
 Node: Bug address1199987
 Node: Usenet1202969
-Node: Maintainers1203746
-Node: Other Versions1205007
-Node: Installation summary1211565
-Node: Notes1212767
-Node: Compatibility Mode1213561
-Node: Additions1214343
-Node: Accessing The Source1215268
-Node: Adding Code1216705
-Node: New Ports1222924
-Node: Derived Files1227412
-Ref: Derived Files-Footnote-11233058
-Ref: Derived Files-Footnote-21233093
-Ref: Derived Files-Footnote-31233691
-Node: Future Extensions1233805
-Node: Implementation Limitations1234463
-Node: Extension Design1235646
-Node: Old Extension Problems1236790
-Ref: Old Extension Problems-Footnote-11238308
-Node: Extension New Mechanism Goals1238365
-Ref: Extension New Mechanism Goals-Footnote-11241729
-Node: Extension Other Design Decisions1241918
-Node: Extension Future Growth1244031
-Node: Notes summary1244867
-Node: Basic Concepts1246042
-Node: Basic High Level1246723
-Ref: figure-general-flow1247005
-Ref: figure-process-flow1247690
-Ref: Basic High Level-Footnote-11250991
-Node: Basic Data Typing1251176
-Node: Glossary1254504
-Node: Copying1286342
-Node: GNU Free Documentation License1323885
-Node: Index1349005
+Node: Maintainers1203973
+Node: Other Versions1205234
+Node: Installation summary1211792
+Node: Notes1212994
+Node: Compatibility Mode1213788
+Node: Additions1214570
+Node: Accessing The Source1215495
+Node: Adding Code1216932
+Node: New Ports1223151
+Node: Derived Files1227639
+Ref: Derived Files-Footnote-11233285
+Ref: Derived Files-Footnote-21233320
+Ref: Derived Files-Footnote-31233918
+Node: Future Extensions1234032
+Node: Implementation Limitations1234690
+Node: Extension Design1235873
+Node: Old Extension Problems1237017
+Ref: Old Extension Problems-Footnote-11238535
+Node: Extension New Mechanism Goals1238592
+Ref: Extension New Mechanism Goals-Footnote-11241956
+Node: Extension Other Design Decisions1242145
+Node: Extension Future Growth1244258
+Node: Notes summary1245094
+Node: Basic Concepts1246269
+Node: Basic High Level1246950
+Ref: figure-general-flow1247232
+Ref: figure-process-flow1247917
+Ref: Basic High Level-Footnote-11251218
+Node: Basic Data Typing1251403
+Node: Glossary1254731
+Node: Copying1286569
+Node: GNU Free Documentation License1324112
+Node: Index1349232
 
 End Tag Table
diff --git a/doc/gawk.texi b/doc/gawk.texi
index 7c7cd30..ad8de26 100644
--- a/doc/gawk.texi
+++ b/doc/gawk.texi
@@ -40576,7 +40576,12 @@ Please do @emph{not} try to report bugs in 
@command{gawk} by posting to the
 Usenet/Internet newsgroup @code{comp.lang.awk}.  Although some of the
 @command{gawk} developers occasionally read this news group, the primary
 @command{gawk} maintainer no longer does.  Thus it's virtually guaranteed
-that he will @emph{not} see your posting.  The steps described here are
+that he will @emph{not} see your posting.
+
+Similarly, posting bug reports or questions in web forums, such
+as @uref{https://stackoverflow.com/, Stack Overflow} may get you
+an answser, but it won't be from the @command{gawk} maintainers,
+who do not spend their time in web forums.  The steps described here are
 the only officially recognized way for reporting bugs.  Really.
 
 @ignore
diff --git a/doc/gawktexi.in b/doc/gawktexi.in
index a03be9f..9cb3f4a 100644
--- a/doc/gawktexi.in
+++ b/doc/gawktexi.in
@@ -39550,7 +39550,12 @@ Please do @emph{not} try to report bugs in 
@command{gawk} by posting to the
 Usenet/Internet newsgroup @code{comp.lang.awk}.  Although some of the
 @command{gawk} developers occasionally read this news group, the primary
 @command{gawk} maintainer no longer does.  Thus it's virtually guaranteed
-that he will @emph{not} see your posting.  The steps described here are
+that he will @emph{not} see your posting.
+
+Similarly, posting bug reports or questions in web forums, such
+as @uref{https://stackoverflow.com/, Stack Overflow} may get you
+an answser, but it won't be from the @command{gawk} maintainers,
+who do not spend their time in web forums.  The steps described here are
 the only officially recognized way for reporting bugs.  Really.
 
 @ignore

-----------------------------------------------------------------------

Summary of changes:
 doc/ChangeLog   |  5 ++++
 doc/gawk.info   | 75 ++++++++++++++++++++++++++++++---------------------------
 doc/gawk.texi   |  7 +++++-
 doc/gawktexi.in |  7 +++++-
 4 files changed, 57 insertions(+), 37 deletions(-)


hooks/post-receive
-- 
gawk



reply via email to

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