public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Trojanowski <bart@jukie.net>
To: linux-kernel@vger.kernel.org
Subject: where is Documentation/REPORTING-BUGS ?
Date: Fri, 27 Feb 2009 13:33:26 -0500	[thread overview]
Message-ID: <20090227183326.GC23376@jukie.net> (raw)

I ran into a regression in 2.6.28..2.6.29-rc6 in vlan code.  I am
bisecting it right now.

While that happens, I wanted to check if the proper way to report it is:
via bugzilla or email.  I went to Documentation and looked for related
material.

>From Documentation/BUG-HUNTING...
> Before you submit a bug report read REPORTING-BUGS.

I'd love to, but it's not there.

The only thing I can find is text from 2003, that predates bugzilla.k.o.

        http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html

If that is still official, maybe it could make its way back into the git
tree.  If not, what's today's preferred bug reporting method?

Cheers,
-Bart

-- 
				WebSig: http://www.jukie.net/~bart/sig/

             reply	other threads:[~2009-02-27 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 18:33 Bart Trojanowski [this message]
2009-02-27 18:44 ` where is Documentation/REPORTING-BUGS ? Randy Dunlap

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=20090227183326.GC23376@jukie.net \
    --to=bart@jukie.net \
    --cc=linux-kernel@vger.kernel.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