On Fri, Jun 1, 2018 at 5:33 PM, <dvh...@infradead.org> wrote: > On June 1, 2018 5:08:32 AM PDT, Stephen Rothwell <s...@canb.auug.org.au> > wrote: >>On Fri, 1 Jun 2018 14:40:35 +0300 Andy Shevchenko >><andy.shevche...@gmail.com> wrote: >>> >>> Oops. What is the proposed fix for that? It seems we can't rebase >>> published branches. >> >>It's unfixable without a rebase, so you could instead consider it an >>opportunity to improve your processes for the future. :-) > > Yeah, in this case we have to do a rebase. > > Andy, I've been wanting to look at using some simple bots and tags for this > kind of thing. GitHub makes this really easy, might be time to move. We'll > continue this offline. > > For now, please rebase next to correct the error as this change is on top of > any of my commits, we won't make things worse by you recommitting my commits.
Done. Author has been informed. -- With Best Regards, Andy Shevchenko
