IMHO the current "Forced update of the master branch" topic of the mailing list is a good reminder to rethink about the current "git commit" / "git push" / "git tag" policy.
I just do compare the git work flow with that from the linux kernel -there both the tag naming and related things (stable release branches) are more easily to understood. Just as an example for confusing people is the tag naming schema. A possible other is the fact, that the current latest "stable" version is 7.2.34, but "git describe" at HEAD just gives "client_release/7.1/7.1.3-2572-ga6da437" -- MfG/Sincerely Toralf Förster pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
