From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] where is kernel source code
Date: Sun, 03 Apr 2005 21:02:36 +0200 [thread overview]
Message-ID: <1112554956.8263.21.camel@pegasus> (raw)
In-Reply-To: <Pine.GSO.4.60.0504012128590.11865@columbia.cs.ubc.ca>
Hi Jack,
> It seems the kernel source code is not maintained in Bluez cvs now, so if
> I want to have a look I should just download linux kernel code. Is that
> right?
look at www.kernel.org or any of the mirrors for example.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-03 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 13:14 [Bluez-devel] Remote name cache ? Frederic Danis
2005-04-02 5:33 ` [Bluez-devel] where is kernel source code Jack Jia
2005-04-03 19:02 ` Marcel Holtmann [this message]
2005-04-03 19:01 ` [Bluez-devel] Remote name cache ? Marcel Holtmann
2005-04-05 12:18 ` Frederic Danis
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=1112554956.8263.21.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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