I agree that the SHAs would be more precise, but they'd be ugly to display on a
public-facing page, and less easy to do diagnosis - the human brain can read
five digits from a monotonic sequence, and get an idea of vintage at a glance,
but it can't do that with non-sequential SHAs.
Perhaps it could be embedded as a comment in the page source, in the same way
as the other php includes? But we would need the latest SHA included in the
server daemon compilation, not just the user web sources.
On Wednesday, 29 March 2017, 11:11, Oliver Bock <oliver.b...@aei.mpg.de>
wrote:
On 29/03/2017 11:55 , Richard Haselgrove wrote:
> Would there be a way to keep the auto-generation of the date and
> author fields, even though the Git SHA isn't helpful in this
> situation?
Yes, use "git log" (see man page for tons of tailoring options).
> Projects also used to show a single SVN number on their server status
> pages, which gave a glimpse of the state of their operational server
> code.
The SHA1s do exactly that, even more precisely.
Best,
Oliver
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
