Deleting branches in git causes gitk to go wild
- by a2h
I decided to delete a few branches from a (personal project) repository of mine that were merged into master after confirming on #git that leftover branches aren't really necessary.
However, gitk's visualisation of my repository's history as a result has been completely screwed up.
Basically something like this:
With those branches from commits appearing out of nowhere eventually going back into some other commits up ahead. A merge did not occur at all of the points, and I only had around 5 extra branches.
Is this normal? Is there any fix for this?