On Mon, 3 Nov 2014 06:42:56 -0800 (PST) Vasily Makarov <einmal...@gmail.com> wrote:
> 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? I'm afraid this question is of so academic we on this list have nothing to do with it. If you think this is a documentation bug, I recommend you to post a message to the main Git list (git at vger.kernel.org). You don't have to be subscribed to it for posting but please make sure your MUA doesn't produce a HTML-formatted message as it will be rejected. See [1] for more info. 1. https://gist.github.com/tfnico/4441562 -- 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.
