Hi, Several patches contains db migration scripts and now we are merging several patches. It leads to branches in db migration scripts. In a usual process, we need to rebase the patch to catch up the latest, but it forces us to do another review and approval.
How about having a special rule that we ignore branches in db migration scripts until G-3 branch cut and fix the branches of db migration scirpts just before/after the branch cut? Thanks Akihiro -- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
