4 ms·
It is to have a single merge commit which is simpler to revert.
by rdtsc 10y ago
It is to have a single merge commit which is simpler to revert.
- falsedan 10y agoIt also stored metadata about the branch (its name) so that you can recover and recreate it if necessary: imagine if you found out that two branches had been merged in the wrong order, and the refs had been deleted. With rebase && --no-ff, the merge commit literally tells you the ref that was attached to the second parent when the merge occurred.