Comment 1 for bug 721611

Basically, you should explain reasons.
I don't accept wrong constitute names and cheating user names.

> INNODB_AUTO_LRU_DUMP
> to
> innodb_enable_fast_warmup

fast? warmup?
I don't like to cheat users. It is really not concrete name.
The name should express the effect cleanly.

> INNODB_EXPAND_IMPORT
> to
> innodb_enable_import_tables

"IMPORT TABLE" is supported basically. It is wrong name.

> INNODB_OVERWRITE_RELAY_LOG_INFO
> to
> innodb_provide_replication_position

I don't like to cheat users. It is really not concrete name.
The name should express the effect cleanly.

> INNODB_PASS_CORRUPT_TABLE
> Rename to innodb_stop_on_corrupt_table=0|1 ( default is 1)

The user should understand passing corrupt table is abnormal for RDBMS...
It may not the problem only about the table.
,as I described before.

InnoDB should abort for all corruption detections.

You should explain the abnormal name for me, again.
You didn't explain any at the previous report.
I don't accept one-side intrusion...

> And next status variables:
>> INNODB_CHECKPOINT_AGE
>> INNODB_CHECKPOINT_MAX_AGE
>> INNODB_CHECKPOINT_TARGET_AGE
>
> Should be
> INNODB_CHECKPOINT_AGE
> INNODB_CHECKPOINT_AGE_MAX
> INNODB_CHECKPOINT_AGE_TARGET

I intended that
values about checkpoint
"age", "max age" and "target age".