The hope was that somebody would put the full 12,000 or so into trac as a redirect table, so that helpdesk and message board volunteers like me could find code areas which might need revisiting. May I remind you that we still have over 300 active tickets in trac, so bughunters are going to be using its search facilities for a while yet. And without redirection, the previous changeset references (the only part of the actual code that trac searches) are going to be useless.
The ten svn changesets in that table are the only ones which can't be used immediately for redirects, because of ambiguity - no primary key is possible until the duplicate references are resolved manually. >________________________________ > From: Oliver Bock <[email protected]> >To: Richard Haselgrove <[email protected]> >Cc: [email protected] >Sent: Monday, 19 November 2012, 12:30 >Subject: Re: [boinc_dev] GIT migration: integration with user web/BBCode links > >On 11/19/12 12:17 , Richard Haselgrove wrote: >> Sorry, table lost formatting in email. Try: >> 26128 6419ac2b4dc248404014f77fa7575adb0056c98f, >> ffc2266a58154aaafbfcafa994da7b6e2c7e20bb > >1) What's the purpose of the 2nd SHA1 again? >2) The same can be done directly like this: > >git log --pretty=format:%H --grep "revision=26128" > > >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. > > > _______________________________________________ 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.
