Changes in:  gstreamer

 gstreamer:fdfc6dc98385816fa3a3765841f40e6c73af58d3
 gst-plugins-base:4c8e211e57146f00fff325403c07217274e9b2f1
 gst-plugins-good:8054cd5df344eafe3b3c4f80e10c47d85797bac2
 gst-plugins-ugly:12509f4a80a4469430bcc6e6f5847955ae60440f
 gst-plugins-bad:af78b45979564035ce4f2535d7257201112f776b
 gst-ffmpeg:520221c47a64e46c23cf120b9e8a497b6af157da
 gnonlin:5d52548056b05a0a2fb7fd901c6b8623c2a1b642
 gst-editing-services:105d901c12d4e9e1f6cdf0681a9e961d80bb6a1e
 gst-python:c889037e40bb3568ef8cd9456123d744b25a919b

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

 commit fdfc6dc98385816fa3a3765841f40e6c73af58d3
Author: Thiago Santos <ts.santos@sisa.samsung.com>
Date:   Thu Jan 23 15:52:51 2014 -0300

    basesrc: preserve seqnum of eos events sent by the user

    Store the eos event seqnum and use it when creating the
    new eos event to be pushed downstream. To know if the eos
    was caused by the eos events received on send_event, a
    'forced_eos' flag is used to use the correct seqnum on
    the event pushed downstream.

    Useful if the application wants to check if the EOS message
    was generated from its own pushed EOS or from another source
    (stream really finished).

    Also adds a test for this

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

commit 5880c9c4c38911bced21854383a5b836d2875f71
Author: Thiago Santos <ts.santos@sisa.samsung.com>
Date:   Thu Jan 23 15:34:27 2014 -0300

    docs: design: add part-seqnums

    Hopefully clarifies how seqnums should be used and copied from
    events to events/messages when those are handled.

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