From: Kieran Kunhya <kierank@obe.tv> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2 2/6] libavformat/sdp: remove whitespaces in fmtp Date: Tue, 14 Nov 2023 22:15:53 +0100 Message-ID: <CAK+ULv5405B7c=ozd7OF2HEJO5aiuNa_DhhfKTQqOP06TeUjiA@mail.gmail.com> (raw) In-Reply-To: <f4ba8aebb07582bdfbbf42f0e52c2b6749a8ecc5.camel@haerdin.se> On Tue, 14 Nov 2023, 21:54 Tomas Härdin, <git@haerdin.se> wrote: > tis 2023-11-14 klockan 17:14 +0100 skrev Kieran Kunhya: > > On Tue, 14 Nov 2023 at 16:47, Tomas Härdin <git@haerdin.se> wrote: > > > > > tis 2023-11-07 klockan 15:12 +0100 skrev Michael Riedl: > > > > Whitespaces after semicolon breaks some servers > > > > > > Which servers? If the spec allows whitespace then the onus is on > > > them > > > to fix their implementations. > > > > > > /Tomas > > > > > > > Poor Tomas, you are not versed in SDP witchcraft where a single > > character > > breaks dozens of devices but fixes dozens of others. > > I have in fact had some contact with SDP, much to my chagrin. This is > also why we should be very strict with it, and be very clear what the > spec says, and/or have the spec changed to reflect reality. With MXF, > being strict has already paid dividends. > > /Tomas > Not comparable IMO, these are embedded IoT devices that will never be fixed. I have spent months of my life debugging a single character issue in SDP. I kid you not. Kieran > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-11-14 21:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-07 14:12 Michael Riedl 2023-11-14 15:47 ` Tomas Härdin 2023-11-14 16:14 ` Kieran Kunhya 2023-11-14 20:53 ` Tomas Härdin 2023-11-14 21:15 ` Kieran Kunhya [this message] 2023-11-14 16:51 ` Rémi Denis-Courmont 2023-11-14 20:51 ` Tomas Härdin 2023-11-15 2:24 ` Romain Beauxis
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='CAK+ULv5405B7c=ozd7OF2HEJO5aiuNa_DhhfKTQqOP06TeUjiA@mail.gmail.com' \ --to=kierank@obe.tv \ --cc=ffmpeg-devel@ffmpeg.org \ /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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git