I noticed one other curious thing while researching a post this morning. Try opening
http://boinc.berkeley.edu/trac/browser/boinc/client/cpu_sched.cpp?rev=8f05a952a89ba7a51e3dfa0e3c84794433d08c12 - that should open boinc / client / cpu_sched.cpp @ 8f05a95 in the trac browser Click 'Previous Revision', and I get the same file open @ revision d84166c6 >From there, click 'Next Revision' - and for me, trac re-displays revision >d84166c6: I can't get any further forward in the file, even back to the >revision I started from. It's just a single (but reproducible) example - I've no idea how widespread it is, but I mention it as something else to check while (or after) the remaining wrinkles in the git migration are sorted out. [I know the hard-core code wizards will prefer to use the git browser, rather than trac - but for us mere mortals, the integrated trac search box covering Changesets / Milestones / Tickets / Wiki is very useful] >________________________________ > From: Oliver Bock <[email protected]> >To: [email protected] >Sent: Monday, 4 March 2013, 16:27 >Subject: Re: [boinc_dev] BOINC-v2 Git Repo Updated > >On 3/1/13 17:20 , Oliver Bock wrote: >> I'll continue my migration this way... > >Update: reached January 2013... > >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. > > > _______________________________________________ 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.
