From: Greg KH <greg@kroah.com>
To: Chase Venters <chase.venters@clientec.com>
Cc: Otto Wyss <otto.wyss@orpatec.ch>, linux-kernel@vger.kernel.org
Subject: Re: OSDL and the Linux kernel community
Date: Sat, 28 Jan 2006 14:51:48 -0800 [thread overview]
Message-ID: <20060128225148.GA5966@kroah.com> (raw)
In-Reply-To: <200601281516.28110.chase.venters@clientec.com>
On Sat, Jan 28, 2006 at 03:16:06PM -0600, Chase Venters wrote:
>
> I read Greg's words on OSDL too, and it seems (from where I stand, anyways)
> that things are going well in that area.
Thanks, I hope so. Only time will tell :)
> But that initiative is focused on the kernel and kernel developers,
> and yours is focused on desktop.
Exactly. Desktop developers already have their own foundatations and
orginizations where discussing desktop things, like tool kits, are best
brought up. This is a kernel specific mailing list and initiative with
OSDL.
thanks,
greg k-h
prev parent reply other threads:[~2006-01-28 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 15:33 OSDL and the Linux kernel community Otto Wyss
2006-01-28 17:10 ` Nick
2006-01-28 21:16 ` Chase Venters
2006-01-28 22:51 ` Greg KH [this message]
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=20060128225148.GA5966@kroah.com \
--to=greg@kroah.com \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=otto.wyss@orpatec.ch \
/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