Bug #40753 The purge backup logs message needs editing
Submitted: 14 Nov 2008 20:12 Modified: 26 Nov 2008 15:59
Reporter: Chuck Bell Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Backup Severity:S3 (Non-critical)
Version:6.0.8 OS:Any
Assigned to: Chuck Bell CPU Architecture:Any

[14 Nov 2008 20:12] Chuck Bell
Description:
The message presented to the user when the command PURGE BACKUP LOGS is issued reads awkward:

mysql> purge backup logs;
Query OK, 0 rows affected (0.05 sec)
All backup logs entries have been deleted.

It should read:

mysql> purge backup logs;
Query OK, 0 rows affected (0.05 sec)
All backup log entries have been deleted.
           ^^^

How to repeat:
mysql> purge backup logs;

Suggested fix:
Change message in errmsg.txt and correct any test results.
[14 Nov 2008 20:18] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/58842

2735 Chuck Bell	2008-11-14
      BUG#40753 : The purge backup logs message needs editing
      
      The message printed when the logs are truncated needs
      to be edited.
[17 Nov 2008 9:44] Jørgen Løland
Good to push
[17 Nov 2008 17:36] Øystein Grøvlen
Patch approved.
[19 Nov 2008 22:08] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/59306

2737 Chuck Bell	2008-11-19
      BUG#40753 : The purge backup logs message needs editing
      
      The message printed when the logs are truncated needs
      to be edited.
[26 Nov 2008 8:50] Bugs System
Pushed into 6.0.9-alpha  (revid:cbell@mysql.com-20081119220805-6y2fxm1eug55b4cs) (version source revid:jorgen.loland@sun.com-20081126084449-lq9ckif3hmxesy1n) (pib:5)
[26 Nov 2008 15:59] Paul DuBois
Cosmetic change. No changelog entry needed.
[10 Dec 2008 5:42] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/61141

2742 He Zhenxing	2008-12-10 [merge]
      Auto Merge