From: Greg KH <gregkh@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: [gentoo-kernel] push kernel bugs upstream sooner and bootsplash/vesa-ng stuff
Date: Thu, 20 Jul 2006 20:28:18 -0700 [thread overview]
Message-ID: <20060721032818.GA7285@kroah.com> (raw)
In-Reply-To: <20060721023732.GB6571@kroah.com>
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
> bit...
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
it.
So, what's the hold up? Why not get them upstream? Would save us a bit
of merge issues for new kernel releases :)
thanks,
greg k-h
--
gentoo-kernel@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-21 3:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 18:19 [gentoo-kernel] Help needed with genpatches Daniel Drake
2006-07-20 18:48 ` Tim Yamin
2006-07-20 19:02 ` Christian Heim
2006-07-20 19:03 ` Mike Doty
2006-07-20 19:00 ` Christian Heim
2006-07-21 2:37 ` Greg KH
2006-07-21 3:28 ` Greg KH [this message]
2006-07-21 7:46 ` [gentoo-kernel] push kernel bugs upstream sooner and bootsplash/vesa-ng stuff Daniel Drake
2006-08-11 21:18 ` Michal Januszewski
2006-07-21 7:29 ` [gentoo-kernel] Help needed with genpatches Daniel Drake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060721032818.GA7285@kroah.com \
--to=gregkh@gentoo.org \
--cc=gentoo-kernel@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox