I will cross-check with the list provided by GitHub. (was doing a similar exercise on the suspect 54 repos anyway)
Luca. On 12 Nov 2013, at 21:27, Kohsuke Kawaguchi <k...@kohsuke.org> wrote: > > As I suggested in the e-mail thread, I've written a little program that looks > at the GitHub events API to figure out the push activities from Luca, and > assembled a list of refs and affected commits. The result is in [1]. > > The exact code is at [2], and I invite others to check my sanity. The basic > idea is to look at the events time line, and find the problematic push. > > The meaning of the output is: > > repository name, before, after, ref > > "before" is the commit that's lost. > > I'm going to compare this with the CSV file from GitHub now to see if there's > a pattern of discrepancy here. > > [1] https://gist.github.com/kohsuke/7438914 > [2] > https://github.com/jenkinsci/backend-git-pushf-finder/tree/eeb462c47dbaa45f2170ccada487eed33da81193 > -- > Kohsuke Kawaguchi http://kohsuke.org/ > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
