No problem, actually I "blame" my discovery on git automated move/copy detection. A copy is typically something suspect unless the copied file is changed a lot (similarity ~50% like in HttpUtil, for instance). I noticed two copies of two files that had been moved a bit earlier, and this was definitely enough to prompt the email.
I'm actually preparing an academic paper on this area, and I'm using shindig as a kind of "lab" for the techniques... Regards Santiago (who should do another PhD in the next years :( ) On Fri, May 23, 2008 at 8:41 PM, Chris Chabot <[EMAIL PROTECTED]> wrote: > Yea i would think so too, don't know what to say other then that it's a bit > of a brown-paper-bag type of mistake. > > Last days of rush before the google io and worked some 36 hours straight > without sleep sessions to get it finished and working for the event (good > news is that php shindig is really in good shape now feature wise, 0.7 is > practically complete now) and in that rush, while i did go through the code > with a fine comb, i overlooked the old files being restored in it. > > -- Chris > > > On May 23, 2008, at 8:22 PM, Santiago Gala wrote: > >> Same exact thing, I thought you would look into the whole commit for >> more suspicious add/renames > >
