> From: Vasily Makarov <einmal...@gmail.com>
> Git documentation defines commit ancestry as "reachability" of one commit
> from another.
> Formally, this might mean that every commit is ancestor and descendant of
> 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?
I believe that "ancestor" and "descendant" are consistently used in
the "inclusive" sense, that is, a commit is its own ancestor and
If the documentation is not consistent in this use, that needs to be
fixed, because not getting that detail right could cause unpleasant
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
For more options, visit https://groups.google.com/d/optout.