A git rebase actually replays the current branch's commits, starting from the commit that diverged from the specified branch, on top of the specified branch. So a rebase rewrites the original history and recalculates the hashes of each commit as it applies them.So in your case newbr never diverged from master so there is nothing to do.
If, however, newbr had commits D1, D2, and D3 like this:
D1--D2--D3 (newbr)
/
A--B--C--D--E (master)
and then afterwards you did "git checkout newbr", then "get rebase master" git would replay D1, D2, then D3 on top of the head of master, which is at E and you would get this:
(master) (newbr)
/ /
A--B--C--D--E--D1--D2--D3
So D1's parent is now different so it has a different hash as opposed to a merge which preserves the branch history. Also, notice how there is no additional merge commit when performing a rebase versus a merge. Hope this helps.