From: akuster808 <akuster808@gmail.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][krogoth] pulseaudio: fix crash when disconnecting bluetooth devices
Date: Tue, 6 Sep 2016 18:18:41 -0700 [thread overview]
Message-ID: <58059020-a29f-e160-9db9-c8b6a865ea70@gmail.com> (raw)
In-Reply-To: <CAP71WjzGB=GOXnwMCV0eZ0MHH76L8fbg3oOokVqxmiSGCXFjDw@mail.gmail.com>
Nicolas,
On 09/06/2016 09:08 AM, Nicolas Dechesne wrote:
> On Tue, Sep 6, 2016 at 5:44 PM, akuster808 <akuster808@gmail.com> wrote:
>> On 09/06/2016 03:00 AM, Tanu Kaskinen wrote:
>>> Ping? I sent this patch for krogoth (and a similar patch for jethro)
>>> about a month ago, but it hasn't been applied yet. This is the first
>>> time I'm sending patches for past releases - are there other hoops to
>>> jump through than adding the [krogoth] tag to the mail subject?
>> I have this sitting in my krogoth-next contrib branch. Did that right before
>> my holiday so I did not send out a message.
> while it is actually useful (and easy) to monitor master-next branch
> since it's in the main repo, it's not the same for the stable -next
> branches.
Correct. There are no next branches for the stable releases. It has been
brought up before to have a common location for maintainers to push so
it can be documented and then the community at large will know where to
look without asking.
> Could these branches be pushed in the main repo or could we
> have a link in a handy place?
git://git.yoctoproject.org/poky-contrib akuster/krogoth-next
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akuster/krogoth-next
>
> and in the short term, where is the current krogoth-next branch?
>
> thx
I hope this helps.
- Armin
next prev parent reply other threads:[~2016-09-07 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 20:41 [PATCH][krogoth] pulseaudio: fix crash when disconnecting bluetooth devices Tanu Kaskinen
2016-09-06 10:00 ` Tanu Kaskinen
2016-09-06 15:44 ` akuster808
2016-09-06 16:08 ` Nicolas Dechesne
2016-09-07 1:18 ` akuster808 [this message]
2016-09-06 19:52 ` Tanu Kaskinen
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=58059020-a29f-e160-9db9-c8b6a865ea70@gmail.com \
--to=akuster808@gmail.com \
--cc=nicolas.dechesne@linaro.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox