From: Romain Beauxis <romain.beauxis@gmail.com>
To: git@haerdin.se
Cc: 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 20:24:33 -0600
Message-ID: <CABWZ6ORYhy5fL4X-fdsYCrmr=GAu2Y7EhuLwx-14vfcUcHJXqw@mail.gmail.com> (raw)
In-Reply-To: <2bee6d91972cf3733272c3be5c891617b24ef3ce.camel@haerdin.se>
Le mar. 14 nov. 2023 à 09:47, Tomas Härdin <git@haerdin.se> a écrit :
>
> 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.
The logic could be inverted: if the specs allow for both but a
majority of users do not accept white space, it would make sense to
change the implementation to maximize compatibility.
> /Tomas
> _______________________________________________
> 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".
_______________________________________________
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".
prev parent reply other threads:[~2023-11-15 2:24 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
2023-11-14 16:51 ` Rémi Denis-Courmont
2023-11-14 20:51 ` Tomas Härdin
2023-11-15 2:24 ` Romain Beauxis [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='CABWZ6ORYhy5fL4X-fdsYCrmr=GAu2Y7EhuLwx-14vfcUcHJXqw@mail.gmail.com' \
--to=romain.beauxis@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=git@haerdin.se \
/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