From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] 2.6.24 merge window
Date: Sat, 20 Oct 2007 16:01:48 +0200 [thread overview]
Message-ID: <1192888909.6184.119.camel@violet> (raw)
In-Reply-To: <bd5b16740710190111h6ae03842g62f04973339ca8aa@mail.gmail.com>
Hi Ohad,
> Is it possible to have a peek at your patches queue for the current 2.6.24
> merge window ?
>
> (I couldn't find it at the usual master branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6)
forgot to push it. Should be there now.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-20 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 8:11 [Bluez-devel] 2.6.24 merge window Ohad Ben-Cohen
2007-10-20 14:01 ` Marcel Holtmann [this message]
2007-10-20 15:16 ` Ohad Ben-Cohen
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=1192888909.6184.119.camel@violet \
--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