All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Grandel <fgrandel@gmail.com>
To: Arman Uguray <armansito@chromium.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: What am I missing?
Date: Tue, 19 May 2015 21:59:13 +0200	[thread overview]
Message-ID: <555B9611.3030504@gmail.com> (raw)
In-Reply-To: <CAHrH25THbWgGgAVjK-G_de6Yxz9m5qHdZV41dRVhO2wmZ9zzbg@mail.gmail.com>

Hi Arman,

On 05/19/2015 09:28 PM, Arman Uguray wrote:
> Hi Florian,
>
>> On Sun, May 17, 2015 at 5:22 PM, Florian Grandel <fgrandel@gmail.com> wrote:
>>>
>>> Hi Florian,
>>>
>>> On Sun, May 17, 2015, Florian Grandel wrote:
>>>> Hi Marcel and Johan,
>>>>
>>>> here is what I did so far:
>>>>
>>>> - I asked you whether contributions from newcomers are welcome (which
>>>> Marcel
>>>> agreed to),
>>>>
>>>> - I coordinated the development target and approach with Marcel to make
>>>> sure
>>>> that my contribution will be generally useful and acceptable,
>>>>
>>>> - I read lots of documentation to make sure that I'm asking as few
>>>> redundant
>>>> questions as possible,
>>>>
>>>> - I invested a considerable amount of time to put a useful contribution
>>>> together,
>>>>
>>>> - Arman invested a considerable amount of time to review it,
>>>>
>>>> - I again invested a considerable amount of time to work in all review
>>>> comments.
>>>>
>>>> - I waited for several weeks and pinged you several times to get you to
>>>> do
>>>> your part as maintainers...
>>>>
>>>> What am I missing?? Did I overlook your response? Or is this the
>>>> "normal"
>>>> Kernel community approach?
>>>
>>> No need to get worried or frustrated about your set. It hasn't been
>>> forgotten about and it hasn't lost the chance to get included in the
>>> first possible kernel release, i.e. 4.2. It'll very likely go into a
>>> bluetooth-next pull request before the 4.2 merge window opens.
>>>
>>> For my part I have no major objections after reading it through a couple
>>> of times - I remember Marcel saying he'd take a look after Arman's
>>> review, which is what I've mostly be waiting for. But in no case has
>>> your set been forgotten.
>>>
>>
>> Ok, cool. Thanks for letting me know. I really got frustrated w/o getting
>> any feedback but now it's ok. :)
>
> Sorry that I couldn't respond to this thread sooner (I've been out
> sick). I feel that the #bluez IRC channel is a good resource in these
> situations where there's long-term radio silence over the mailing
> list. The maintainers are generally very active on the channel
> (assuming you're in their time zone) and they usually respond to your
> messages pretty quickly. So feel free to give that a shot. You can
> find more info on the IRC channels here: http://www.bluez.org/contact/
>
> As far as your patches go, I don't have any more comments beyond the
> ones that I left earlier and you've already addressed them, so it's up
> to Marcel to take a look now.
Thanks for your feedback. I'll test #bluez next time. :-)

Florian

      reply	other threads:[~2015-05-19 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-17 13:32 What am I missing? Florian Grandel
2015-05-17 13:46 ` Johan Hedberg
2015-05-18  0:22   ` Florian Grandel
2015-05-19 19:28     ` Arman Uguray
2015-05-19 19:59       ` Florian Grandel [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=555B9611.3030504@gmail.com \
    --to=fgrandel@gmail.com \
    --cc=armansito@chromium.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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.