On 2/26/13 16:07 , Rom Walton wrote: >> In general: do you agree with me that, eventually, the *content* of > boinc.git and boinc-v2.git should be identical when comparing their > latest common commits/trees? > > Yes, migration isn't complete until the source code matches up.
Good. > The main areas of difference right now appear to be: > 1. Files that were missing from the first migration and haven't been > added to v1 yet Ok, those should be responsible when whole files are missing. FYI: so far I found the following v1 commits that fixed svn/v1-migration issues and should therefor be excluded from v2, sometimes only partially: > 6d778ea > 4e11eba > 2c7b2a0 > 4904c8c > 5fd09cf > c99db95 (Rom added only "stage_file" to v2, missing files untouched) > 6168e24 (Rom added/touched none of the new files to v2) > bdaaa5c > e4fc688 (Rom added only "db_schemaversion.php to v2, missing files untouched) > d622531 Can you confirm this list? Is it correct and complete? > 2. Line feed issues imported from SVN Can you elaborate on this? Why should there be a difference between v1 and v2 because of this? > 3. RCSID tags. (If the files haven't been modified since CVS days their > tags are $id$, if they were brought into existence post SVN# 12399 then > they have an SVN RCSID tag value) Same question: why should there be a difference between v1 and v2 because of this? > 4. One source commit dealing with intel_gpu variable renames. It looks > like it was part of a merge commit and not handled by the patch > mechanism. > 5. One source commit adding the new WCG skin to the source tree. Please provide the SHA1 in v1 and v2 for reference. Thanks, 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.
