After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 746347 - dashdemux: set default @startNumber and also avoid wrong overwrite
dashdemux: set default @startNumber and also avoid wrong overwrite
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other All
: Normal normal
: 1.5.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-03-17 13:48 UTC by xixi
Modified: 2015-03-24 19:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
set default startNumber and also avoid wrong overwrite (1.51 KB, patch)
2015-03-17 13:55 UTC, xixi
needs-work Details | Review
patch_with_full_name (1.51 KB, patch)
2015-03-17 14:28 UTC, xixi
committed Details | Review

Description xixi 2015-03-17 13:48:36 UTC
It's related to commit[793b4bca93530a5e30b5ba8ea02983cbd11532db].
This commit fixed the default @startNumber to 1 as spec requires. 
 
However, it will overwrite "parent"'s @startNumber.
 
Consider this scenario: AdaptationSet has SegmentTemplate with @startNumber to 0, and Representation has SegmentTemplate with @startNumber missing.
The @startNumber of the Representation should be inherited from AdaptationSet.
But that git commit will set it to 1, overwriting an inherited value.
Comment 1 xixi 2015-03-17 13:55:37 UTC
Created attachment 299600 [details] [review]
set default startNumber and also avoid wrong  overwrite

a candidate patch is attached.
 
It will set default @startNumber to 1, if @startNumber is missing at all level.
Also, it will avoid incorrect overwriting inherited value.
Comment 2 Tim-Philipp Müller 2015-03-17 14:03:00 UTC
Comment on attachment 299600 [details] [review]
set default startNumber and also avoid wrong  overwrite

>From: xixi <xixi10111011@gmail.com>

Is this ("xixi") your full name? If not, could you please use git commit --amend --author='...' and put your full name there? (and then also run git config --global user.name "..." so it's set properly in future, thanks)
Comment 3 Thiago Sousa Santos 2015-03-17 14:15:48 UTC
Review of attachment 299600 [details] [review]:

Looks good. Could you provide a new patch with your full name so it is properly documented in git?
Comment 4 xixi 2015-03-17 14:28:22 UTC
Created attachment 299603 [details] [review]
patch_with_full_name

patch with full name replaced
Comment 5 xixi 2015-03-17 14:34:31 UTC
@Tim-Philipp Müller @Thiago Sousa Santos 
Thanks for your review and advice, and I've added a new patch with full name.
Comment 6 Thiago Sousa Santos 2015-03-24 19:55:38 UTC
commit 9e6198d9efc29a7f5f541a71a87a6187f4828e3b
Author: Jun Xie <xixi10111011@gmail.com>
Date:   Tue Mar 17 21:49:40 2015 +0800

    dashdemux: set default @startNumber and also avoid wrong overwrite
    
    Set default @startNumber to 1, if @startNumber is missing at all level.
    Also avoid incorrect overwriting inherited value.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=746347