{"thread":{"id":"37648","subject":"Strange behavior of git rev-list --first-parent --ancesty-path","startedAt":"2014-09-30T05:25:12Z","lastAt":"2014-09-30T05:25:12Z","messageCount":1,"participants":["Василий Макаров"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"250012","messageId":"CABEtfDGwtMTSP5xxme-p60iU1gMXBwCXA0cGHxLuZS+j-KwhGQ@mail.gmail.com","threadId":"37648","inReplyTo":null,"subject":"Strange behavior of git rev-list --first-parent --ancesty-path","fromName":"Василий Макаров","fromEmail":"einmalfel@gmail.com","sentAt":"2014-09-30T05:25:12Z","receivedAt":"2014-09-30T05:25:12Z","isPatch":false,"sender":{"key":"einmalfel@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2640813?v=4"},"body":"Hello!\n\nImagine following tree:\nA--B--C\n \\      /\n  D--E\nB is parent #1 of C.\n\ngit rev-list --first-parent --ancestry-path D..C returns zero commits.\nThis is correct, since one cannot find any commits between D and C\ntraversing tree by first parent.\ngit rev-list --first-parent --ancestry-path E..C returns SHA of C.\nThis is strange, because --ancestry-path should restrict output to\ncommits being both ancestors of C and descendants of E.\n\nGit did not return me any errors or warnings so I'm assuming that\n--first-parent and --ancestry-path are OK to be used together.\n\nSo, is it a git bug or I'm doing smth wrong?\n"}]}