> While doing further consistency checks I found the following v2
commit:
> >
http://boinc.berkeley.edu/gitweb/?p=boinc-v2.git;a=commit;h=723c1f5667
> > 2c6853e203578693254653f0680e04
>
> Where does it come from? I can't find it at all in v1:
> >
http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=history;f=lib/network.
> > cpp

SHA1: 131f868eee1f472fb5900959c995bcdcb3f126cc

...

I've cloned your repo and am taking a look.

----- Rom

-----Original Message-----
From: Oliver Bock [mailto:[email protected]] 
Sent: Friday, March 01, 2013 11:20 AM
To: Rom Walton
Cc: [email protected]
Subject: Re: [boinc_dev] BOINC-v2 Git Repo Updated

Update:

While doing further consistency checks I found the following v2 commit:
> http://boinc.berkeley.edu/gitweb/?p=boinc-v2.git;a=commit;h=723c1f5667
> 2c6853e203578693254653f0680e04

Where does it come from? I can't find it at all in v1:
> http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=history;f=lib/network.
> cpp

Also, the way you generated the patches (straight git format-patch)
linearized the history and changed the order of several commits (a known
effect). In contrast, I replayed the original history as close as
possible which makes it easier to do v1/v2 cross-checks:

> https://gitmaster.atlas.aei.uni-hannover.de/einsteinathome/boinc-v2/gr
> aph/brevilo/master

Comparing your v2 with my v2 I also found a number of white-space
changes, presumably introduced while you edited/recreated the patches
manually, something I usually didn't have to do. I only used
combinations of format-patch/am and cherry-pick with v1 SHA1s, no need
to construct new patches.

I also noticed changes in the order of checkin_notes entries but those
shouldn't have much relevance anymore.

Check (diff) these two commits if you want to see for yourself:
Oliver-v2: bee9118
Rom-v2:    cb092b5

I validated my migration so far against v1 (ignoring added files):
> git diff --stat --diff-filter=CDMRTUXB f3f40f0..bee9118

The few differences found are all either mode changes or removals of the
RCSID - no actual changes in content.

I'll continue my migration this way...


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