Final update (for the time being):

On 3/6/13 18:15 , Oliver Bock wrote:
> I finished the 7.0a and wxWidgets30 migration, so these as well as
> master and 7.0b are now available, alongside their respective tags:
> 
>> https://gitmaster.atlas.aei.uni-hannover.de/einsteinathome/boinc-v2/commits/master
> 
> I did some preliminary sanity-checking and they all look good to me so
> far. I'll push those upstream to v2 tomorrow.

I updated the master and client_release/7/7.0b branches to their current
commits (i.e. tag client_release/7.0/7.0.54) and pushed everything upstream.

We're now ready to start sanity checking!

To summarize, these are the branches and tags I managed manually:

master
client_release/7/7.0a
client_release/7/7.0b
SimpleButtonFix
charlief/wxwidgets30

client_release/7.0/7.0.37
client_release/7.0/7.0.38
client_release/7.0/7.0.39
client_release/7.0/7.0.40
client_release/7.0/7.0.41
client_release/7.0/7.0.42
client_release/7.0/7.0.43
client_release/7.0/7.0.44
client_release/7.0/7.0.45
client_release/7.0/7.0.46
client_release/7.0/7.0.47
client_release/7.0/7.0.48
client_release/7.0/7.0.49
client_release/7.0/7.0.50
client_release/7.0/7.0.51
client_release/7.0/7.0.52
client_release/7.0/7.0.53
client_release/7.0/7.0.54
last-svn-commit/7.0a
last-svn-commit/7.0b
last-svn-commit/master
last-svn-commit/wxwidgets30


Known minor/irrelevant differences to v1 (comparing master):

* I didn't retain the original author details of merge commits (sorry)
* File modes of 8 files changed from 644 to 755, like db/init_db
* v1 still lacks 7 files which exist in v2, like html/ops/white.css
* 35 files contain RCSIDs in v1, removed/emptied in v2


We're almost there, so let's verify this repo as good as we can and
finalize the migration. I invite everyone to help scrutinizing v2.


Cheers,
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.

Reply via email to