|
|
|
|
|
by keybored
619 days ago
|
|
I think both are done for long-term forks. Since both are done we can surmise that both are practical. I suspect that rebase-forks are more common historically. Because the only thing I’ve heard of when it comes to managing changes on top of a version control system (which could be centralized) are “patch queues” or stacks. And those tend to be rebase systems with a different system. But I have no practical experience with long-lived forks. |
|