public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
To: Meino Christian Cramer <mccramer@s.netic.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.64p5 No USB support when APIC mode enabled
Date: 08 Mar 2003 14:48:10 +0100	[thread overview]
Message-ID: <1047131289.3544.14.camel@rousalka> (raw)
In-Reply-To: <20030308.132939.75185771.mccramer@s.netic.de>

[-- Attachment #1: Type: text/plain, Size: 2095 bytes --]

Le sam 08/03/2003 à 13:29, Meino Christian Cramer a écrit :
> From: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
> Subject: Re: 2.5.64p5 No USB support when APIC mode enabled
> Date: 07 Mar 2003 19:57:37 +0100
> 
> Hi Nicolas.
> 
>  ..._I_ am the stupid one, Nicolas :)
> 
>  Could you pleas e give me a short hint, how I should handle
>  what I have found (USB probs) with the bugzilla interface.
>  Haven't used it before...

Bugzilla is very user-unfriendly at first but one get used to it and
it's very powerful (plus lots of projects use it)

Usually when you have found a problem you should :

1. Search if it's not already reported (query, usually search by
summary/description gets the broadest results)

2. If you find a bug that looks the same :
* add yourself to the CC list
* add a comment stating your problem and why you think it's the same

If it's not the same problem the maintainer which knows best will tell
you to open another bug (so if you're not sure, ask about it in your
comment)

3. if you didn't find any similar problem open a new bug. The important
parts are
* Fill it in the best category so it will be directed to the good person
* Use a « catchy » summary which makes clear what the problem is
* Attach relevant files (often dmesg, kernel config, lspci)
* Only specify the person to whom the bug should be assigned if you're
sure of what you're doing (ie this person is already treating similar
bugs) ! Bad assignment will loose time and annoy people, and bugzilla
will try to select the right maintainer based on the category you've
chosen if you leave the field blank.

Note bugzilla is very flexible ; if you made mistakes the bug will be
reclassified/redirected till it's filled correctly (however this will
take time)

Moreover note bugzilla usage for the kernel is fairly recent. Some
maintainers are still not used to it, so they'll also make mistakes.

Last hint : all bugzilla fields are commented, usually a link right next
to each field will lead to an explanation.

Regards,

-- 
Nicolas Mailhot

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-03-08 13:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 18:57 2.5.64p5 No USB support when APIC mode enabled Nicolas Mailhot
2003-03-08 12:29 ` Meino Christian Cramer
2003-03-08 13:48   ` Nicolas Mailhot [this message]
2003-05-20 18:26 ` 2.4.21-pre5/7 fails to compile Meino Christian Cramer
2003-05-21 13:02   ` Carl-Daniel Hailfinger
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07 14:11 2.5.64p5 No USB support when APIC mode enabled Nicolas Mailhot
2003-03-07 15:19 ` Meino Christian Cramer
2003-03-06 13:03 2.5.64 - xircom realport no workie well CaT
2003-03-06 13:29 ` Russell King
2003-03-07  7:44   ` 2.5.64p5 No USB support when APIC mode enabled Meino Christian Cramer
2003-03-07 12:52     ` Alan Cox
2003-03-07 13:37       ` Meino Christian Cramer

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=1047131289.3544.14.camel@rousalka \
    --to=nicolas.mailhot@laposte.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mccramer@s.netic.de \
    /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