On 29/03/2017 17:11 , Christian Beer wrote: > The SHA1 would still be the best way to show the version but is not > useful because of the way git works. Every project obviously has a clone > of the main BOINC repository but they won't just checkout this and use > it on their production webserver. They probably have a separate branch > in this repository where they track project specific files and changes > to BOINC files. This way it is easy to see differences between BOINC and > the project and also inspect changes done to BOINC. New changes coming > in from BOINC can then be merged into a testing branch and after testing > into the production branch with a simple "git merge master". This way a > project can always fall back to the last known good configuration if > something goes bad. In this scheme the SHA1s are useless because they > are specific for this non-public repository and won't help any external > troubleshooter.
That's the point. Yet this isn't a disadvantage of git. It's in fact a huge advantage over svn since what's described above simply wasn't easily possible with svn, making project maintenance much more error prone. And even svn IDs in the old days only represented a file's version in its original state (when copied into the webroot) which could have easily been customized, without a visible trace. Cheers, 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.
