Christian Couder [off-list ref] writes:
Junio wrote:
>
> Although I fully realize that the established semantics of A..B in git is
> bottom-exclusive, top-inclusive, and this suggestion breaks the UI
> uniformity by deviating from that convention, I have to wonder if it would
> be more useful if you let the bottom commit (A in your example) also be
> skipped.
I agree that it would be perhaps more usefull to skip the bottom commit.
Actually I do not think it is such a big deal to warrant more code and
complexity. "skip A..B A", if you really wanted to, would work anyway.