Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] package/libopusenc: bump to version 0.2.1
Date: Tue, 01 Jan 2019 21:34:47 +0100	[thread overview]
Message-ID: <87wonop15k.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190101211531.788b58de@windsurf> (Thomas Petazzoni's message of "Tue, 1 Jan 2019 21:15:31 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > Hello,
 > On Tue, 01 Jan 2019 21:10:41 +0100, Peter Korsgaard wrote:
 >> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:  
 >> 
 >> > This release fixes two minor bugs:
 >> > - a gapless bug in the LPC filtering
 >> > - a crash on destroy when using the pull API  
 >> 
 >> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>  
 >> 
 >> Committed, thanks.
 >> 
 >> Does this depend on opus 1.3

 > I don't think it does, it's really a point release with two bug fixes.

 >> / should this be added to the 2018.02.x / 2018.11.x branches?

 > Considering it's a bugfix only release, perhaps.

Ok, I'll backport it.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2019-01-01 20:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01 14:36 [Buildroot] [PATCH 1/4] package/opus: bump to version 1.3 Thomas Petazzoni
2019-01-01 14:37 ` [Buildroot] [PATCH 2/4] package/libopusenc: bump to version 0.2.1 Thomas Petazzoni
2019-01-01 20:10   ` Peter Korsgaard
2019-01-01 20:15     ` Thomas Petazzoni
2019-01-01 20:34       ` Peter Korsgaard [this message]
2019-01-01 14:37 ` [Buildroot] [PATCH 3/4] package/opusfile: bump to version 0.11 Thomas Petazzoni
2019-01-01 20:11   ` Peter Korsgaard
2019-01-01 14:37 ` [Buildroot] [PATCH 4/4] package/opus-tools: bump to version 0.2 Thomas Petazzoni
2019-01-01 20:12   ` Peter Korsgaard
2019-01-01 20:09 ` [Buildroot] [PATCH 1/4] package/opus: bump to version 1.3 Peter Korsgaard

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=87wonop15k.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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