I know this feels a bit anal retentive, please bear with me…
It seems that if the last changed branch is not a tip, the whole line graph for that branch is thin and dashed.
In the case of this screenshot, I rebased pixart on top of master, which created a bold branch to the top left (before it was to the right, being a branch spun out of master earlier on, the remote-tracking branch is still there).
I also had a branch called import-new-features which was before the tip of pixart (also seen on the right with the remote-tracking branch). To update it's location, I used the "Set Tip" on the corresponding commit of the newly rebased branch. This cause the branch import-new-features to be the left-most, and since it's not a bold-line change, it has a thin dash line. The problem is that it doesn't stop at the juncture with pixart, it goes all the way down to the beginning of time, and you can see white breaks due to the commits dots. I would need to make some commits on either branch to solve the visual glitch.
Another way to go about it would be rebasing import-new-features instead of pixart, set pixart's tip to import-new-features and then cherry-pick the commits from the remote-tracking branch. With a couple of commits it's fine, with a more a complex history it becomes a bit tedious.
I know this feels a bit anal retentive, please bear with me…
It seems that if the last changed branch is not a tip, the whole line graph for that branch is thin and dashed.
In the case of this screenshot, I rebased
pixarton top ofmaster, which created a bold branch to the top left (before it was to the right, being a branch spun out of master earlier on, the remote-tracking branch is still there).I also had a branch called
import-new-featureswhich was before the tip ofpixart(also seen on the right with the remote-tracking branch). To update it's location, I used the "Set Tip" on the corresponding commit of the newly rebased branch. This cause the branchimport-new-featuresto be the left-most, and since it's not a bold-line change, it has a thin dash line. The problem is that it doesn't stop at the juncture withpixart, it goes all the way down to the beginning of time, and you can see white breaks due to the commits dots. I would need to make some commits on either branch to solve the visual glitch.Another way to go about it would be rebasing
import-new-featuresinstead ofpixart, setpixart's tip toimport-new-featuresand then cherry-pick the commits from the remote-tracking branch. With a couple of commits it's fine, with a more a complex history it becomes a bit tedious.