Old upstream released a 1.11 version, too

Question

Old upstream released a 1.11 version, too

eMPee584 opened this issue 8 years ago · 3 comments

+swapspace (1.11) stable; urgency=high
+  * Use posix_fallocate() to save writing to swap file.
+
+ -- Jeroen T. Vermeulen <jtv@...>  Wed, 03 Jun 2015 09:20:00 +0700

Answer 1 · 2018-02-10T18:05:50.000Z

Changes adopted in 385085c

Answer 2 · 2018-02-11T09:26:36.000Z

That doesn't quite solve the confusion of what the relevant upstream of swapspace is..
Could you rebase your tree on origin?

Answer 3 · 2018-02-11T21:17:12.000Z

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 ***@***.***> 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.