title: Push new history after rebase?
body: <p>I pushed some changes to our central git repository, and then immediately realized that I had an old, now obsolete change lying around, and that I had introduced a merge with it:</p>
  
  <p><img src="https://i.stack.imgur.com/b7tCP.png" alt="before"></p>
  
  <p>I then used git rebase to get rid of this spurious parent:</p>
  
  <p><img src="https://i.stack.imgur.com/HH6xT.png" alt="after"></p>
  
  <p>Then I pushed this with <code>git push -f</code> to origin. It answers with "everything up-to-date".</p>
  
  <p>Now I would expect the central repository to match what I have locally. However, when I <code>clone</code> the project anew, I still have the spurious parent inside. What's worse is that git wants to merge, and if I let it do that, I get my latest commit twice (once with the old hash, and once with the new one after rebasing).</p>
  
  <p>How do I get git to push what I have without merging, and just take my repository state as the new state (so basically, to reject all <em>remote</em> differences)?</p>
  
  <p>or am I doing this wrong? I want to get rid of the "When reading a property..." commit, and the whole red line in the upper image.</p>