Contributors mailing list archives
Re: Alternative 8.0-9.0 migration procedureby
Acsone SA, Stéphane Bidoul
Normally yes, git log <path> does that. To be tested.
On Wed, Sep 14, 2016 at 11:08 AM Pedro M. Baeza (Tecnativa) <email@example.com> wrote:
I haven't tested it yet also. One thing I have doubts now: does it filter commits for including only the current module (but not commit affecting several modules)?Regards.2016-09-14 10:53 GMT+02:00 Stéphane Bidoul <firstname.lastname@example.org>:Thanks for the feedback Pedro.By the way I have not tested it but I think it works also if the module being migrated does not yet exist on the 9.0 branch.-sbiI have tried your procedure, Stephane, and it works very well, so for me we can switch the current procedure (I wrote it) with yours. I have only added one step to ensure 8.0 branch exists before making the rest of the steps.Regards.2016-09-12 16:53 GMT+02:00 Jairo Llopis <email@example.com>:I recently experienced difficulties with the usual migration procedure.I got a similar problem for updating the website_slides backport (so it's not exactly the "usual" procedure).Here's my solution, although it is in Spanish (I bet you know how to use Google Translator ;)Indeed the process needs some polishing. Filtering by date may work most times, but sometimes the merge takes place after that date, but the commit you are merging took place before, so it would get excluded.