From: Steve Hancock <perltidy@users.sourceforge.net>
Date: Mon, 7 Sep 2020 00:58:33 +0000 (-0700)
Subject: update docs to include ref to git issue #
X-Git-Tag: 20200907.01~52
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=0a2d22f96a0f7e712993922552039fd2a3791027;p=perltidy.git

update docs to include ref to git issue #
---

diff --git a/CHANGES.md b/CHANGES.md
index 03a9210f..753500a3 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -2,8 +2,8 @@
 
 ## 2020 09 07
 
-    - Fixed a bug when the combination -scbb -csc was used.  It occurs in perltidy
-      versions 20200110, 20200619, and 20200822.  What happens is
+    - Fixed bug git #37, an error when the combination -scbb -csc was used.
+      It occurs in perltidy versions 20200110, 20200619, and 20200822.  What happens is
       that when two consecutive lines with isolated closing braces had new side
       comments generated by the -csc parameter, a separating newline was missing.
       The resulting script will not then run, but worse, if it is reformatted with
diff --git a/docs/ChangeLog.html b/docs/ChangeLog.html
index c36bf85c..af434945 100644
--- a/docs/ChangeLog.html
+++ b/docs/ChangeLog.html
@@ -2,8 +2,8 @@
 
 <h2>2020 09 07</h2>
 
-<pre><code>- Fixed a bug when the combination -scbb -csc was used.  It occurs in perltidy
-  versions 20200110, 20200619, and 20200822.  What happens is
+<pre><code>- Fixed bug git #37, an error when the combination -scbb -csc was used.
+  It occurs in perltidy versions 20200110, 20200619, and 20200822.  What happens is
   that when two consecutive lines with isolated closing braces had new side
   comments generated by the -csc parameter, a separating newline was missing.
   The resulting script will not then run, but worse, if it is reformatted with