All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/live555: bump to version 2020.08.19
Date: Tue, 29 Sep 2020 21:03:11 +0200	[thread overview]
Message-ID: <87lfgsv21c.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200922214315.6c1407bb@windsurf> (Thomas Petazzoni's message of "Tue, 22 Sep 2020 21:43:15 +0200")

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

 > On Mon, 21 Sep 2020 10:32:57 +0200
 > Michael Nosthoff via buildroot <buildroot@busybox.net> wrote:

 >> According to changelog this version fixes memory leaks and buffer overflows.
 >> - http://live555.com/liveMedia/public/changelog.txt
 >> 
 >> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
 >> ---
 >> package/live555/live555.hash | 4 ++--
 >> package/live555/live555.mk   | 2 +-
 >> 2 files changed, 3 insertions(+), 3 deletions(-)

 > Applied to master, thanks.

Committed to 2020.08.x, thanks.

This notice in the changelog isn't very nice though :/

2020.08.09:
- Changed the parameter signature of the "RawVideoRTPSink" constructor and "createNew()"
  functions so that the "width" parameter comes before the "height" parameter.  This order
  - "width", "height" - is more common, and is the order used when these parameters are
  defined in RFC 4175.
  IMPORTANT NOTE: Because the types of these two parameters are the same, existing application
  code that uses "RawVideoRTPSink" will compile without error; however, it will not work
  properly unless the order of the parameters in the call to "RawVideoRTPSink::createNew()"
  is changed.
 
-- 
Bye, Peter Korsgaard

      reply	other threads:[~2020-09-29 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  8:32 [Buildroot] [PATCH v2] package/live555: bump to version 2020.08.19 Michael Nosthoff
2020-09-22 19:43 ` Thomas Petazzoni
2020-09-29 19:03   ` Peter Korsgaard [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=87lfgsv21c.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 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.