Possibility to downliad exact commit over http allows easy integrate with packaging systems when some unreleased but already commited patches needs to be integrated into generate packages.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Integration of unreleased but already committed patches had been a solved problem 10 years before git even existed. The proper way to do it is to include just the patch that's needed, not everything that's been pushed since the last release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As well it does not provide automatic informing about new tags/releases (from that point of view I would choose github)
And why do you need this? Contrary to most github projects, we do have this thing called releases (with accompanying tarballs).
Anyway, we're not going to move the project--and cause needless work for all downstreams--just based on a single request...
Possibility to downliad exact commit over http allows easy integrate with packaging systems when some unreleased but already commited patches needs to be integrated into generate packages.
Integration of unreleased but already committed patches had been a solved problem 10 years before git even existed. The proper way to do it is to include just the patch that's needed, not everything that's been pushed since the last release.