[debian-mysql] factoring out mysql-common

Otto Kekäläinen otto at seravo.fi
Tue Jun 14 13:26:25 UTC 2016


Hello!

2016-06-14 14:58 GMT+03:00 Andreas Beckmann <anbe at debian.org>:
>> I've just looked at this now. I'm disappointed that the history is lost.
>> Can we instead base this tree from mysql-5.7's tree - just strip out
>> everything not wanted in a branch, and refactor the remaining into a
>> mysql-common? Then "git blame" etc will still work.

I don't mind either way. Git blame will anyway not go beyond mysql-5.5
contents, but at least we would have the history for the last couple
of years and maybe indeed the majority of changes to mysql-common
contents was done in recent years. If Andreas or Robie wants to
refactor the mysql-common repo to be based on the mysql-5.7 repo,
please do it. All the git magic works as long the repos have a common
ancestor, they don't need to permanently live on branches in the same
repo.

>> Second, can we start keeping things in a single git repo rather than
>> creating yet another one? How about we continue to use mysql-5.7 but
>> have a "common" branch? Then eventually perhaps we can move mariadb into
>> the same git tree too.

This would work if we would have been vice enough to forsee this
layout and base MariaDB work on the MySQL 5.5. or 5.6 repo so that
they would have a common git ancestor, but we didn't, and I don't
think it is feasible to convert at this point anymore.



More information about the pkg-mysql-maint mailing list