you really do not want to know the git crimes i was up to today
@aescling oh you probably need to use rebase --onto trunk commit-you-rebased-from-last-time
@aescling rebase starts from the last common commit which will be basically the fork point in our case
rebase --onto b a only rebases the changes since a onto the branch b
@aescling this is something i recently had to research because at work we have this same problem
@Lady i’ll have to make sure to try that out sometime
merging 3.5.3+glitch onto 3.5.2+glitch sure is a time if