summaryrefslogtreecommitdiff
path: root/mysql-test/r/innodb-autoinc-optimize.result
diff options
context:
space:
mode:
authorJoerg Bruehe <joerg@mysql.com>2009-01-15 19:11:25 +0100
committerJoerg Bruehe <joerg@mysql.com>2009-01-15 19:11:25 +0100
commit4f0d2f5a03ce0ded7138dbabb416534cb09abf75 (patch)
tree41abac2dd671718f9634fdcac0c8a46da0c285b6 /mysql-test/r/innodb-autoinc-optimize.result
parent4c4e4881f19801a5ff7a209488567d024a141f19 (diff)
parent4ecaa45d11e3ead0d128e9535f8f0e35767c00ad (diff)
downloadmariadb-git-4f0d2f5a03ce0ded7138dbabb416534cb09abf75.tar.gz
Upmerge changesets from 5.0-build to 5.1-build.
This does not bring any contents changes, it is purely metadata which are affected. Details: Even within 5.0, most of these changesets did not cause file contents changes, because they were backports done for the "service pack" builds of 5.0.66sp1 and 5.0.72sp1. The "real" changesets are also already present in 5.1, so this upmerge doesn't change any contents. The only "real" changeset in 5.0 was a fix of the shell scripts used to configure bdb (BerkeleyDB). As we completele removed bdb from the 5.1 sources already, the affected files are not present in the 5.1 source tree, so this changeset also does not cause any contents changes.
Diffstat (limited to 'mysql-test/r/innodb-autoinc-optimize.result')
0 files changed, 0 insertions, 0 deletions