This message got caught up in a moderation backlog last week, because of the 
size of the attachment. Re-posting for the list - I can supply the SVN-->GIT 
lookup table separately (csv file) to anyone who would find it useful.


----- Forwarded Message -----
>From: Richard Haselgrove <[email protected]>
>To: BOINC Dev MailingList <[email protected]> 
>Cc: DavidAnderson <[email protected]>; RomWalton 
><[email protected]> 
>Sent: Thursday, 15 November 2012, 17:00
>Subject: GIT migration: integration with user web/BBCode links
> 
>
>Following up a query from a user this morning, I found that message board 
>links of the type [trac]changeset:12345[/trac] no longer work - see 
>http://boinc.berkeley.edu/dev/forum_thread.php?id=7989
> 
>It also appears that the BBCode parsing engine doesn't like the new 
>alphanumeric formats. Searching trac for 'BBCode' in an attempt to find the 
>source code for the parsing engine, the only references came in the form of 
>SVN changesets - which of course no longer work....
> 
>1) (simple) If anyone can find the parsing code, could they change the [trac] 
>tag to accept alpha-numberic strings?
> 
>2) (longer term) The new style changesets like 7f6ab8d (or even 
>7f6ab8d49eeaa6df58bf3bc4f61f2f7540d2c7e7) have, where appropriate, antecedant 
>references like "svn path=/trunk/boinc/; revision=25601", which is fine and 
>dandy for historical import checking: but it's of no practical use for finding 
>current code.
> 
>This isn't just pedantry: code versions are still referenced by SVN revision 
>number in a number of places, like the default Server Status page layout, and 
>the hidden page design tagging on user web pages.
> 
>What's needed is an automatic linkage and page forwarding mechanism to 
>translate *from* SVN revisions *to* matching GIT records.
> 
>I attach a first draft version of a lookup table which could be used to 
>achieve this. It can't be used directly 'as is', because it can't have a key 
>index: ten (only) of the ~12,000 records have multiple forward references. 
>They are:
> 
>261286419ac2b4dc248404014f77fa7575adb0056c98f, 
>ffc2266a58154aaafbfcafa994da7b6e2c7e20bb
>26129690341f17870e981dc04047a4a8274b16d2a5442, 
>b339b891883140f6ac853025ad236d9a4b3a1f92
>261300bddda60ea838a7eeb6a87e53b07eaa6a7749959, 
>865e8d3b21e67f316d1182baee61630a33afed2f
>26133735f33940b00cfe9cd96a83a48f8a227bf608c65, 
>bd37aa80174f56fb1c54e4af15246bedd2c4038c
>2613429fcecc1349d3deb542c492bd2e7196c95b9588f, 
>9a5c7b27b02d3b839ac84f6667c038efed3aeb3a
>261355ded1db2976453b099d91bc14d9ad0dec1deb4c7, 
>c322ec0c70cc83afdf551802c7a22cf3f92ca72e
>26136320f342f0394d9fbe408f9f77a9812b1c8ee0334, 
>588e07d43b83af83d487dcab29de4afc0404fb7d
>2614794b0fd72ec06ae8a46d43545a8e945c7dc9c653e, 
>e902b5dcbe87e6d8cc207ae244506556347cbc6f
>26149318312ea9bd23eefd0dafed3b102dc9e131edd69, 
>7f28847cc6575c16c6b70080d9d48b462223c88c
>261536ff3ad7da399956b12ba09a1520382464d6e372b, 
>c21979514e9fcd7c79b44118a1690e7d4b820612
> 
>The alternative destinations will have to be checked by eye, because with the 
>non-sequential GIT identifiers, one can't tell at a glance which is the newer 
>version. But I hope this gives a platform to work from.
>
>
_______________________________________________
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