Lars Schneider <larsxschneider@xxxxxxxxx> writes: > git diff branchA...branchB > --> gives me the diff between (the common ancestor of A and B) and B. That means I never see changes on branchA. > > git log branchA...branchB > --> gives me the commits reachable from A and B. That includes changes from branchA. > > Is this because of a design decision that I do not (yet) understand or is this inconsistent for historical reasons? git diff operates on two revisions. That is inherently incompatible with the usual meaning of A...B and A..B, which are set operations on the revision history. That git diff accepts this syntax is only for convenience. Andreas. -- Andreas Schwab, schwab@xxxxxxxxxxxxxx GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html