3 ms·

More like merges but actually neither… it can reorder patches, even conflicting ones, it’s a completely foreign concept in git.

• 1oooqooq 3y ago
  sounds like rebase with force push remote. (well, every push is a force push in git. so just rebase+push. ...except on github if you have "protected branches")
  • baq 3y ago
    Not really, no; ordering of patches is not something you as a developer should care about. It’s behind the scenes. No force pushes necessary.
    • 1oooqooq 3y ago
      thanks. i will have to try it out. but it does sound like "rewriting history" in git et al.
      • baq 3y ago
        The point is there is no single history in the git sense - there are patches which commute, but their order is... irrelevant (if possible).