On Tue, Sep 26, 2017, at 02:18 AM, Zhenguo Niu wrote: > It's very appreciated if you shed some light on what the next steps would > be to move this along.
We should schedule a period of time to freeze the Mogan repo, update the replacement master (if necessary) then we can either force push that over the existing branch or push it into a new branch and have you propose and then merge a merge commit. Considering that the purpose of this is to better update the history of the master branch the force push is likely the most appropriate option. Using a merge commit will result in potentially complicated history which won't help with the objective here. What is a good time to freeze, update and push? In total you probably want to allocate a day to this, we can likely get by with less but it is easy to block off a day and then we don't have to rush. Clark __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
