kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: insane79@yandex.ru (Dennis Semakin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Is kernel Bugzilla a good way to start?
Date: Fri, 23 Dec 2016 11:31:19 +0300	[thread overview]
Message-ID: <2102861482481879@web26h.yandex.ru> (raw)
In-Reply-To: <1482424201.15012.15.camel@surriel.com>

Ok, thanks. But actually I was confused and disappointed little bit when opened kernel bugzilla.
I found old and very old bugs and I don't suppose that they are actual. 
As for education and understanding how kernel sub-systems works it could be very useful try to fix some of them.
 

22.12.2016, 19:30, "Rik van Riel" <riel@surriel.com>:
> On Thu, 2016-12-22 at 19:21 +0300, Dennis Semakin wrote:
>> ?Hi everybody.
>> ?I just thought that may be it will be quicker to start to develop for
>> ?kernel.
>
> It can be, but one word of caution. ?Sometimes bugs
> get fixed independently from the bug report, and the
> bug described in the bug report may no longer be
> happening in the current kernel.
>
> It would be good to test the bugs people have filed,
> to make sure they still exist, before trying to "fix
> them again" :)
>
> --
> All rights reversed

  reply	other threads:[~2016-12-23  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 16:21 Is kernel Bugzilla a good way to start? Dennis Semakin
2016-12-22 16:30 ` Rik van Riel
2016-12-23  8:31   ` Dennis Semakin [this message]
2016-12-22 16:30 ` Peter Senna Tschudin
2016-12-23  8:36   ` Dennis Semakin
     [not found] ` <9013.1482427538@turing-police.cc.vt.edu>
2016-12-23  9:01   ` Dennis Semakin

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=2102861482481879@web26h.yandex.ru \
    --to=insane79@yandex.ru \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).