Solved Git: ranges in cgit

[grahamperrin]

Two full stops, three full stops (to signify a range):

• <https://cgit.freebsd.org/src/log/?qt=range&q=eb86c6c5b462..5f7ac491eef4>
• <https://cgit.freebsd.org/src/log/?qt=range&q=eb86c6c5b462...5f7ac491eef4>

No visible difference, in this case.

Is there a logical difference?

 

[T-Aoki]

Official documentation doesn't seem to exist, but found this archived mail.
Maybe just looking for .. as delimiter between strings which looks correct git hash, ignoring single ..

 

[Andriy]

Two full stops, three full stops (to signify a range):

• <https://cgit.freebsd.org/src/log/?qt=range&q=eb86c6c5b462..5f7ac491eef4>
• <https://cgit.freebsd.org/src/log/?qt=range&q=eb86c6c5b462...5f7ac491eef4>

No visible difference, in this case.

Is there a logical difference?

The results are the same because there is linear history between those two commits.
Double and triple dot commit ranges (or, rather, sets) are explained, for example, in Pro Git book.