All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Next BlueZ developer meeting
Date: Mon, 05 Jul 2010 22:28:22 -0300	[thread overview]
Message-ID: <1278379702.2789.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1278363322.2789.23.camel@localhost.localdomain>

Hello again,

> our next BlueZ developer meeting will be held as mini-summit as part of
> the LinuxCon in Boston.
> 
> 	http://events.linuxfoundation.org/events/linuxcon/mini-summits
> 
> I like to invite interested developers to join us in Boston. The summit
> will be held on Sunday, 8th and Monday, 9th of July.

I obviously meant 8th and 9th of August. Sorry for the confusion.

Regards

Marcel



  reply	other threads:[~2010-07-06  1:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 20:55 Next BlueZ developer meeting Marcel Holtmann
2010-07-06  1:28 ` Marcel Holtmann [this message]
2010-07-08  2:22   ` Marcel Holtmann
2010-08-06 22:19     ` Ron Shaffer
2010-08-07  5:12       ` Marcel Holtmann
2010-08-07  5:48         ` Ron Shaffer
2010-08-07 13:01           ` Marcel Holtmann
2010-08-07 13:29             ` Manuel Naranjo
2010-08-07 22:10             ` Arun Kumar

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=1278379702.2789.27.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.