Git documentation defines commit ancestry as "reachability" of one commit from another. Formally, this might mean that every commit is ancestor and descendant of itself. I've also checked git merge-base --is-ancestor and found it returns "true" for same commit passed twice as argument.
This is formal although not so evident detail, and IMO it changes meaning of some git commands/options. Does anybody have any thoughts on this? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
