Changes in:  gstreamer

 gstreamer:9e125e7bab92259d2d3317c2bf47da081c03ba8a
 gst-plugins-base:472ded1cf333a35e328a21084f46a28dd5febfef
 gst-plugins-good:2bc631bcd0051cbb6cf2e519bf103cfdf3c33f08
 gst-plugins-ugly:7e3811cc21d82604ac6bff6fde6b60307fc9c958
 gst-plugins-bad:8663611af50f0b510b432e8318ef0f019292a5e6
 gst-ffmpeg:8025ac289bee401f6511ee319c2d6c9c93a97322
 gnonlin:5d52548056b05a0a2fb7fd901c6b8623c2a1b642
 gst-editing-services:14a2f5943d97318ce87d268f9dd17629a94c5800
 gst-python:c889037e40bb3568ef8cd9456123d744b25a919b

====== gstreamer =============

 commit 9e125e7bab92259d2d3317c2bf47da081c03ba8a
Author: Sebastian Dröge <sebastian@centricular.com>
Date:   Thu Jan 2 13:34:52 2014 +0100

    pad: Add unit test for adding/removing blocking probes while a pad is blocked

    And make sure that these new probes are actually called if they should
    instead of silently blocking the pad forever.

    https://bugzilla.gnome.org/show_bug.cgi?id=721289

commit 93ce90f83320e845867d28b9cbeea5b596a1ef04
Author: Sebastian Dröge <sebastian@centricular.com>
Date:   Thu Jan 2 13:33:20 2014 +0100

    pad: Check if new probes need to be called when adding/removing some

    This allows blocking a pad, add a new blocking probe, removing
    the first probe and then having the second probe called. Which
    could then decide that data-flow should actually continue
    instead of blocking now.

    https://bugzilla.gnome.org/show_bug.cgi?id=721289