{"thread":{"id":"4144","subject":"align git diff a..b semantics with git log a..b","startedAt":"2006-05-15T08:41:35Z","lastAt":"2006-05-15T08:41:35Z","messageCount":1,"participants":["Salikh Zakirov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"19980","messageId":"44683EBF.9070307@Intel.com","threadId":"4144","inReplyTo":null,"subject":"align git diff a..b semantics with git log a..b","fromName":"Salikh Zakirov","fromEmail":"salikh.zakirov@intel.com","sentAt":"2006-05-15T08:41:35Z","receivedAt":"2006-05-15T08:41:35Z","isPatch":false,"sender":{"key":"salikh.zakirov@gmail.com","avatar":null},"body":"Hi,\n\nCurrently, git-diff accepts\n\n\tgit-diff A..B\n\nsyntax, and the output seems to be equivalent of 'git-diff A B'.\n\nIMHO, this conflicts with A..B semantics defined for git-log family of commands.\nConsider following tree\n\nO--X--Y--A1--A2  (a)\n       \\\n        B1--B2  (b)\n\nThe command 'git log a..b' will show B1,B2, so I would find it\nintuitive (and useful) to have 'git diff a..b' show B1+B2,\nrather than -A2-A1+B1+B2.\n\nSo, I suggest to change semantics of 'git diff a..b'\nto 'git diff `git-merge-base a b` b'.\n\nI could contribute the documentation change if the idea is accepted and implemented.\n\nThanks a lot!\n"}]}