OP here (of the blog post). “git merge-base” behaves better with this approach if the commits you supply happen to span orphan branches.
Probably my tool (and git merge-base) almost never need it. I feel a bit as if I’m Randall Munroe keeping velociraptor repellent spray near my person at all times just in case…
So the only real pro-arguments here are “it looks cool and my tools sometimes need it”?
Seems like a pretty useful argument. What’s the cost?
OP here (of the blog post). “git merge-base” behaves better with this approach if the commits you supply happen to span orphan branches.
Probably my tool (and git merge-base) almost never need it. I feel a bit as if I’m Randall Munroe keeping velociraptor repellent spray near my person at all times just in case…