Introducing RedPatch (Ksplice Blog)

Posted Nov 10, 2012 5:05 UTC (Sat) by devferret (guest, #77830)
In reply to: Introducing RedPatch (Ksplice Blog) by geofft
Parent article: Introducing RedPatch (Ksplice Blog)

All true. But really: "At Oracle, we feel everyone in the Linux community can benefit from the work we already do to get our jobs done, so now we’re sharing these broken-out patches publicly..."

I mean, there's spin, and then there's propaganda, and then you sort of fall off the end of the scale and the tummy trouble starts...

Introducing RedPatch (Ksplice Blog)

Posted Nov 16, 2012 8:28 UTC (Fri) by jrn (subscriber, #64214) [Link] (2 responses)

> I mean, there's spin, and then there's propaganda, and then you sort of fall off the end of the scale and the tummy trouble starts...

What is misleading about it? I might be naïve, but to me it *does* seem useful to be able to conveniently look up what changes went into the kernel a large number of users are testing. It also means there is a git repository I can point to and ask people to bisect in. And if I end up needing to develop against RHEL for some reason, "git blame" will finally work.

Introducing RedPatch (Ksplice Blog)

Posted Nov 16, 2012 14:53 UTC (Fri) by smurf (subscriber, #17840) [Link] (1 responses)

> What is misleading about it?

At the very least, it's misleading propaganda because Oracle is doing to MySQL this very same thing which RedHat does to the kernel. So Oracle being self-righteous about it won't wash.

RH does it to annoy Oracle, and Oracle does it to annoy MariaDB.

Introducing RedPatch (Ksplice Blog)

Posted Nov 19, 2012 3:40 UTC (Mon) by mathstuf (subscriber, #69389) [Link]

I don't know that its fully analogous since Oracle is MySQL upstream and can fully deny/hide patches while Red Hat is not kernel upstream and pushes applicable patches upstream, so its not as if there's *no* information there.