From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] alsa-lib: 1.0.29 -> 1.1.0
Date: Thu, 14 Jan 2016 14:45:30 +0200 [thread overview]
Message-ID: <5697986A.7010603@linux.intel.com> (raw)
In-Reply-To: <1452774089.11077.100.camel@iki.fi>
On 01/14/2016 02:21 PM, Tanu Kaskinen wrote:
>>> Changelog: http://alsa-project.org/main/index.php/Changes_v1.0.29_v
>>> 1.1.0
>>
>> What about all the other alsa-* recipes?
>
> They are coming.
It's more convenient if you send them in a single batch, with a branch
to pull from (using scripts/(create|send)-pull-request). Less manual
cherry-picking in the email client for Ross.
Alex
next prev parent reply other threads:[~2016-01-14 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 6:52 [PATCH] alsa-lib: 1.0.29 -> 1.1.0 Tanu Kaskinen
2016-01-14 11:11 ` Alexander Kanavin
2016-01-14 12:21 ` Tanu Kaskinen
2016-01-14 12:45 ` Alexander Kanavin [this message]
2016-01-14 13:06 ` Burton, Ross
2016-02-12 12:11 ` alexander.kanavin
2016-02-12 11:34 ` Tanu Kaskinen
2016-01-14 12:41 ` [PATCH v2] " 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=5697986A.7010603@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--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