From: Dave Jones <davej@codemonkey.org.uk>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Ryan Anderson <ryan@michonline.com>,
linux-kernel@vger.kernel.org, postmaster@vger.kernel.org
Subject: Re: sparse errors
Date: Wed, 28 May 2003 15:51:48 +0100 [thread overview]
Message-ID: <20030528145148.GA30092@suse.de> (raw)
In-Reply-To: <3ED4C921.5080902@gmx.net>
On Wed, May 28, 2003 at 04:35:13PM +0200, Carl-Daniel Hailfinger wrote:
> > It probably shouldn't be CC'd to linux-kernel, but there isn't any other
> > place either.
> Maybe create a new list:
>
> linux-source-analyzers@vger.kernel.org
>
> or something like that.
kernel-janitor-discuss@lists.sf.net has been used in the past for discussion
of such things a few times.
Dave
next prev parent reply other threads:[~2003-05-28 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 5:38 sparse errors Ryan Anderson
2003-05-28 14:16 ` Linus Torvalds
2003-05-28 14:35 ` Carl-Daniel Hailfinger
2003-05-28 14:51 ` Dave Jones [this message]
2003-05-28 14:39 ` Linus Torvalds
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=20030528145148.GA30092@suse.de \
--to=davej@codemonkey.org.uk \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=postmaster@vger.kernel.org \
--cc=ryan@michonline.com \
--cc=torvalds@transmeta.com \
/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