All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel bugzilla
Date: Mon, 20 Jun 2005 22:59:38 +0400	[thread overview]
Message-ID: <200506202259.38682.adobriyan@gmail.com> (raw)
In-Reply-To: <20050618112342.6a4d088f.akpm@osdl.org>

On Saturday 18 June 2005 22:23, Andrew Morton wrote:
> Alexey Dobriyan <adobriyan@gmail.com> wrote:
> > On Saturday 18 June 2005 01:39, Andrew Morton wrote:
> > > We should encourage people to use bugzilla as the initial
> > > entry-point.  But if someone instead uses email as the first contact I'm
> > > just a little bit reluctant to say "thanks, now go and try again".
> > > 
> > > Perhaps we could find some nice volunteer (hint) who could take the task of
> > > transferring such reports into bugzilla.
> > 
> > Andrew, I'm going to file
> > 
> > 	Subject: 2.6.12: connection tracking broken?
> > 	Subject: 2.6.12 cpu-freq conservative governor problem
> > 	Subject: PROBLEM: libata + sata_sil on sil3112 dosen't work proper
> > 	Subject: [2.6.12] x86-64 IO-APIC + timer doesn't work
> > 
> > around monday evening if there would be no activity.
> 
> Sounds good, thanks - let us know how it goes.
> 
> It'll need to be coordinated with the reporter in some way.  It may end up
> too confusing.
> 
> > Do I understand correctly that the procedure is
> > 
> > 	1. Search for duplicates
> > 	2. Choose category
> > 	3. Add "From: Joe Reporter <>" at the beginning, copy-paste email.
> > 	4. Add Joe and relevant lists to CC.

Craaap.

"The name <mailing list> is not a valid username. Either you misspelled it,
or the person has not registered for a Bugzilla account."

Same for Joe Reporter. :-(

> > 	5. Profi^WCommit
> > 
> > and bugzilla won't shoot unsuspecting guys afterwards?
> 
> I think so.  I've never entered a bug ;)

  reply	other threads:[~2005-06-20 18:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050617001330.294950ac.akpm@osdl.org>
     [not found] ` <1119016223.5049.3.camel@mulgrave>
     [not found]   ` <20050617142225.GO6957@suse.de>
2005-06-17 21:10     ` kernel bugzilla Andrew Morton
2005-06-17 21:23       ` Jens Axboe
2005-06-17 21:39         ` Andrew Morton
2005-06-18 14:50           ` Alexey Dobriyan
2005-06-18 18:23             ` Andrew Morton
2005-06-20 18:59               ` Alexey Dobriyan [this message]
2005-06-18 15:45           ` Adrian Bunk
2005-06-18 15:58             ` Martin J. Bligh
2005-06-17 21:45         ` Martin J. Bligh
2005-06-18 19:13           ` Dave Jones
2005-06-19  2:54             ` Kyle Moffett
2005-06-19  8:22               ` Dave Jones
2005-06-19 16:58                 ` Kyle Moffett
2005-06-20 11:58             ` Takashi Iwai
2005-06-20 14:08               ` Martin J. Bligh
2005-06-18  1:14         ` Herbert Xu
2005-06-19 19:02 Kenneth Parrish
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 23:04 Andrew Morton
2003-05-13 21:55 ` Diego Calleja García

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=200506202259.38682.adobriyan@gmail.com \
    --to=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.