Closed eMPee584 closed 6 years ago
Changes adopted in 385085c712437a784307c71dc319d036e1440455
That doesn't quite solve the confusion of what the relevant upstream of swapspace is.. Could you rebase your tree on origin?
I’m not sure why there’s confusion. The form happened in 2014 and then upstream made a release in 2015, whose changes I merged back into the fork. I can’t see what advantage there would be to rewriting history. It’s quite a few git commits and I’d rather not go messing around with rebase just to make the fork seem “cleaner”
Jacob
On Feb 11, 2018, at 04:26, Marcel Partap notifications@github.com wrote:
That doesn't quite solve the confusion of what the relevant upstream of swapspace is.. Could you rebase your tree on origin?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.