On Sat, 19 Jun 2010 10:14:31 +0200, Sergei Golubchik <serg@stripped> wrote:
> I guess, somebody upgraded innodb_plugin in MySQL source tree to a new
> version (from innodb svn, perhaps?), and instead of replacing files
> under bzr nose (rm -rf innodb_plugin; cp -r ~/new/innodb_plugin .)
> decided to inform bzr that old tree is deleted (bzr rm -force innodb_plugin).
> Somebody may speculate that it was done to complicate the work of
> maintaining forked innodb_plugin branches, but I personally don't
> attribute it to malice.
I think it's been replaced with a converted and merged InnoDB source
tree. So instead of InnoDB dev going on in a separate tree and then
occational giant "import innodb" changesets, InnoDB source is now just
directly merged into the MySQL tree.
I've seen evidence of this tracking through the logs of 5.5 at
least. My guess would be that this is the same for 5.1.
Of course, it would have been really nice if this was all explained on
internals@ for those of us closely following InnoDB development but I've
long since given up hope of internals@ being a list discussing, well,
development and internals.