Bug #40508 Formatting improvements in ascii version of change log
Submitted: 4 Nov 2008 17:39 Modified: 10 Nov 2008 17:34
Reporter: Kent Boortz Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[4 Nov 2008 17:39] Kent Boortz
Description:
The ascii version of the CHANGELOG could be made easier to read, with
some formatting changes

- Removal of the "filling" of lines, i.e. change

   * Some   warnings   were   being   reported   as   errors.
   * Some warnings were being reported as errors.

- An empty line between items, i.e. each "*" but also before and
   after sub listings and even between those sub items, like

  * Incompatible Change: The tables for MySQL Backup logging have
    been renamed, and the logging capabilities now are more
    flexible, similar to the capabilities provided for the general
    query log and slow query log.
       + The names of the MySQL Backup log tables in the mysql
         database have been changed from online_backup and
         online_backup_progress to backup_history and
         backup_progress.
       + Logging now can be enabled or disabled, it is possible to
         log to tables or to files, and the names of the log files
         can be changed. For details, see Section 6.3.3.1, "MySQL
         Backup Log Control."
       + A new statement, FLUSH BACKUP LOGS, closes and reopens
         the backup log files. A new option for mysql_refresh(),
         REFRESH_BACKUP_LOG, performs the same operation.
  * Important Change: The --skip-thread-priority option is now
    deprecated in MySQL 5.1 and is removed in MySQL 6.0 such that
    the server won't change the thread priorities by default.

  to

  * Incompatible Change: The tables for MySQL Backup logging have
    been renamed, and the logging capabilities now are more
    flexible, similar to the capabilities provided for the general
    query log and slow query log.

       + The names of the MySQL Backup log tables in the mysql
         database have been changed from online_backup and
         online_backup_progress to backup_history and
         backup_progress.

       + Logging now can be enabled or disabled, it is possible to
         log to tables or to files, and the names of the log files
         can be changed. For details, see Section 6.3.3.1, "MySQL
         Backup Log Control."
  
       + A new statement, FLUSH BACKUP LOGS, closes and reopens
         the backup log files. A new option for mysql_refresh(),
         REFRESH_BACKUP_LOG, performs the same operation.
  
  * Important Change: The --skip-thread-priority option is now
    deprecated in MySQL 5.1 and is removed in MySQL 6.0 such that
    the server won't change the thread priorities by default.

How to repeat:
See example above
[10 Nov 2008 17:34] Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.