All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3
Date: Tue, 07 Jul 2015 16:23:42 +0300	[thread overview]
Message-ID: <559BD2DE.8080801@linux.intel.com> (raw)
In-Reply-To: <cover.1436195315.git.tanu.kaskinen@linux.intel.com>

On 07/06/2015 06:14 PM, Tanu Kaskinen wrote:
> These patches update speex to 1.2rc2 and speexdsp to 1.2rc3. speexdsp
> was previously included in speex, but now it's in a separate source
> tree, so a new recipe is needed.

The gap between rc1 and rc2 has been six *years*, and rc2 has been 
released 7 *months* ago. The upstream clearly doesn't know the 
definition of 'release candidate' :)

I'm totally fine with your patches, just in case.


Alex


  parent reply	other threads:[~2015-07-07 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 15:14 [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3 Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 1/3] speexdsp: initial recipe Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 2/3] speex: 1.2rc1 -> 1.2rc2 Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 3/3] alsa-plugins, pulseaudio: depend on speexdsp, not speex Tanu Kaskinen
2015-07-07 13:23 ` Alexander Kanavin [this message]
2015-07-09  7:58 ` [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3 Richard Purdie
2015-07-09  8:11   ` Tanu Kaskinen
2015-07-09 10:49     ` Tanu Kaskinen
2015-07-11 22:42       ` Richard Purdie
2015-07-15  7:40       ` Richard Purdie
2015-07-15  8:25         ` Andre McCurdy
2015-07-22  7:02           ` Richard Purdie

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=559BD2DE.8080801@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 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.