k is used twice

Bug #1336860 reported by Max Bubenick on 2014-07-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Data Dumper
Max Bubenick

Bug Description

{ "no-locks", 'k', 0, G_OPTION_ARG_NONE, &no_locks, "Do not execute the temporary shared read lock. WARNING: This will cause inconsistent backups", NULL },
105107 { "long-query-guard", 'l', 0, G_OPTION_ARG_INT, &longquery, "Set long query timer in seconds, default 60", NULL },
106108 { "kill-long-queries", 'k', 0, G_OPTION_ARG_NONE, &killqueries, "Kill long running queries (instead of aborting)", NULL },

both are using k, this was introduce with no-locks. We need to change it to K

Related branches

Changed in mydumper:
milestone: none → 0.6.2
assignee: nobody → Max Bubenick (max-bubenick)
importance: Undecided → Medium
status: New → Triaged
Max Bubenick (max-bubenick) wrote :

kill-long-queries was changed from k to K

Changed in mydumper:
status: Triaged → Fix Committed
Changed in mydumper:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers