nopy/android_frameworks_base — comment on commit ad26a5b524ced788c4d1244bdd001cf01fc0805b
File:  line 0
By TwistedUmbrella:

They are all available on my GitHub, sorry to ruin your analogy.
On Dec 16, 2011 3:17 PM, "Keyan Mobli" <
reply@reply.github.com>
wrote:

> Well given that this patched leaked twice, once in it's completed form
> (this one) and once when it wasn't completed (a different one) people can't
> correctly follow the history of a patch that was never intended for public.
> This one was, and if you look at our github, it is merged there publically
> too.
>
> If you're upset at this, it would be like me asking for all your WIP
> patches on your current machine.
>
> On Fri, Dec 16, 2011 at 2:15 PM, TwistedUmbrella <
> reply@reply.github.com
> > wrote:
>
> > Quote kmobs: "I was just curious as to how one of our patches leaked."
> > You are correct in that it was a generalization, but it is hard to
> > separate the tool from the garage when it makes up part of the repair
> > process.
> > Oh well. I just learned a valuable lesson today. Thanks.
> >
> > ---
> > Reply to this email directly or view it on GitHub:
> >
> >
> https://github.com/nopy/android_frameworks_base/commit/ad26a5b524ced788c4d1244bdd001cf01fc0805b#commitcomment-802045
> >
>
>
>
> --
> *Keyan Mobli*
>
> University of Texas at Austin Undergraduate
> Neurobiology Major
>
> CyanogenMod Android Developer
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/nopy/android_frameworks_base/commit/ad26a5b524ced788c4d1244bdd001cf01fc0805b#commitcomment-802051
>