public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "André Dahlqvist" <andre.dahlqvist@telia.com>
To: linux-kernel@vger.kernel.org
Subject: Re: bug reports for CML2?
Date: Fri, 28 Dec 2001 13:39:18 +0100	[thread overview]
Message-ID: <20011228123918.GA12276@telia.com> (raw)
In-Reply-To: <20011228121228.GA9920@emma1.emma.line.org> <Pine.LNX.4.33.0112280724180.24465-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0112280724180.24465-100000@localhost.localdomain>

rpjday <rpjday@mindspring.com> wrote:

> is there a formal place to discuss issues with CML2, including submitting
> bug reports when it generates python tracebacks?

The "How To Report Bugs" section in the READ.ME file that comes with
CML2 says that they should be reported to Eric.
-- 

André Dahlqvist <andre.dahlqvist@telia.com>


  reply	other threads:[~2001-12-28 12:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 10:18 zImage not supported for 2.2.20? Roy Hills
2001-12-28 12:12 ` Matthias Andree
2001-12-28 12:26   ` bug reports for CML2? rpjday
2001-12-28 12:39     ` André Dahlqvist [this message]
2001-12-28 13:11 ` zImage not supported for 2.2.20? Roy Hills
2001-12-28 13:35   ` Matthias Andree
2001-12-28 14:32   ` Petri Kaukasoina
2001-12-28 20:13     ` Wolfgang Erig
2001-12-29  2:23       ` H. Peter Anvin
2002-01-01 15:16         ` Wolfgang Erig
2001-12-28 17:44   ` Roy Hills
2001-12-28 18:19     ` Alan Cox
2001-12-28 20:36       ` Petri Kaukasoina
2001-12-29  2:25         ` H. Peter Anvin
2001-12-29  2:58           ` Alan Cox
2001-12-29 11:01           ` Petri Kaukasoina
2001-12-28 18:36     ` H. Peter Anvin
2001-12-28 19:04       ` Alan Cox
2001-12-28 18:42     ` H. Peter Anvin
2001-12-31  9:12     ` Roy Hills
2002-01-02  0:54       ` H. Peter Anvin
2001-12-31 12:16     ` Roy Hills
2001-12-31 13:06       ` Petri Kaukasoina

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=20011228123918.GA12276@telia.com \
    --to=andre.dahlqvist@telia.com \
    --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