How do you rebase the current branch's changes on top of changes being merged in?

You've got what rebase does backwards git rebase master does what you're asking for — takes the changes on the current branch (since its divergence from master) and replays them on top of master then sets the head of the current branch to be the head of that new history. It doesn't replay the changes from master on top of the current branch.

You've got what rebase does backwards. Git rebase master does what you're asking for — takes the changes on the current branch (since its divergence from master) and replays them on top of master, then sets the head of the current branch to be the head of that new history. It doesn't replay the changes from master on top of the current branch.

LOL. Ouch. Thanks for correcting me.

Just when I thought that I was getting the hang of it all... – Jonathan M Davis Sep 4 at 4:33 @Jonathan it's cool. This is a little bit of a tricky topic. By the way, git rebase working would move master's changes (after the point that working branched off) to be on top of the working branch — but that's not a very sensible thing to do to master :) – hobbs Sep 4 at 5:00.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.