On Thu, Jul 20, 2006 at 07:37:32PM -0700, Greg KH wrote:
> Oh, also, some stuff that affected us came up at the kernel summit with
> regards to how we should track our kernel bugs. I'll write it up in a
So the main bit that happened, was an agreement to allow the
bugzilla.kernel.org database, hold distro kernel bugs. The upstream
developers want to see the bugs earlier, and faster. So I'd really
recommend throwing them there almost immediately if we can, unless it's
obvious the problem is in our stuff (bootsplash, vesa-ng, etc.).
The big issue is that the reporter would have to create their own
account there to get notified of changes, and mirroring the stuff back
into our bugzilla would get to be a big chore. So I'd recommend just
starting out with a few of them, and see how it goes.
There should be a new field in the kernel.org bugzilla there soon that
shows that this is a gentoo specific bug (along with the other distros.)
If it doesn't happen in a week, poke me and I'll go poke the responsible
people for it.
Another off-hand remark that happened was a conversation about the
bootsplash and vesa-ng code. People were wondering why the hell it
wasn't in mainline already! The bootsplash stuff was remarked by the
whole group involved that it looked great, and was way better than the
old implementation. Yeah, I know some RH people still don't like the
whole idea, as they use X for their splash stuff, but it shouldn't be
hard to keep that under control, as I think the code is pretty
self-contained with no real issues if you turn it off.
And the same for vesa-ng, although most present were not even aware of
So, what's the hold up? Why not get them upstream? Would save us a bit
of merge issues for new kernel releases :)
email@example.com mailing list