2012-01-31 10:43 UTC+0100 Viktor Szakats (harbour syenar.net)

* INSTALL
    * typo and minor tweak to troubleshooting section

harbour/ChangeLog

@@ -16,6 +16,10 @@
    The license applies to all entries newer than 2009-04-28.
 */
 
+2012-01-31 10:43 UTC+0100 Viktor Szakats (harbour syenar.net)
+  * INSTALL
+    * typo and minor tweak to troubleshooting section
+
 2012-01-31 05:07 UTC+0100 Przemyslaw Czerpak (druzus/at/poczta.onet.pl)
   * harbour/src/pp/ppcore.c
     ! fixed line numbering in extended codeblocks with multiline
@@ -33,16 +37,16 @@
     + Added: ::lQuitting message handelling.
   * contrib/hbide/ideharbourhelp.prg
     + Implemented: to save all Harbour help documents to .pdf.
-       User will be asked to provide a file name which will be 
-       used as prefix to complete .pdf filename. It will be suffixed 
-       with "_" + function name. User is requested to select an 
-       empty sub-folder to get all PDFs which will be over 2000+ 
+       User will be asked to provide a file name which will be
+       used as prefix to complete .pdf filename. It will be suffixed
+       with "_" + function name. User is requested to select an
+       empty sub-folder to get all PDFs which will be over 2000+
        as per current SVN.
   * contrib/hbide/idemain.prg
     + Reworked: how hbIDE was exiting. It may fix the exit crash.
   * contrib/hbide/idesaveload.prg
-    + Fixed: a wrongly accesses class variable. 
-       This might potentially be causing hbIDE to generate GPF at 
+    + Fixed: a wrongly accesses class variable.
+       This might potentially be causing hbIDE to generate GPF at
        startup on Windows 7, please test.
   * contrib/hbide/ideshortcuts.prg
     + Added: ::lQuitting message handelling.

harbour/INSTALL

@@ -1292,10 +1292,10 @@ HARBOUR
        Complete log output is rarely necessary, but always make sure to include
        the top of the output (lines starting with '!') and the area where
        problematic behavior occurred _first_. Make sure to not only include
-       a link failure or a make tool failure only, as it's most of the time
-       not enough information. Compress your log using zip if it is larger
+       a link failure or a make tool failure, as it's most of the time not
+       enough information. Compress your log using zip if it is larger
        than 25KB. (use the extension .zip)
-       Without these, your chances are lower to get useful or any response.
+       With these, you have much better chance to get useful or any response.
    10. If you are to report a build problem with a Harbour application,
        most of the above point applies, plus make sure to use '-trace'
        command line option when running hbmk2.