Hi Gianfranco, I'd like to comment on your statements, although I'll leave it to the BOINC devs to provide an "official" answer.
> Gianfranco Costamagna wrote, On 06.03.13 14:09: >> Hi everybody, since some days I'm thinking about your switch to git, >> with the benefits that this has implied. >> >> Anyway this approach still have some problems e.g.: >> - there is no automatic tag at each release, with a link for the >> source downloading. Each client release is tagged: http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=tags Making these tags available for download is just be a matter of configuring gitweb (the web front-end linked above) to allow that. Rom, I recommend you enable that feature: http://git-scm.com/docs/gitweb.conf.html >> - people cannot contribute. Why not? You can always send in patches using "git format-patch". You can also always fork the repo and publish your fork/branches/changes elsewhere, like on GitHub. You may then issue a merge request via mail to boinc_dev and get your changes pulled from your remote. Agreed, it's not as integrated and convenient as doing this all on GitHub itself but it works nevertheless. I reckon BOINC has decided against hosting their repo on GitHub for a reason, but I'll let them comment on that part. HTH, Oliver _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
