On Sat, Feb 13, 2016 at 06:01:36PM +0100, Stefano Sabatini wrote:
> On date Saturday 2016-02-13 17:01:59 +0100, Michael Niedermayer encoded:
> > Signed-off-by: Michael Niedermayer <mich...@niedermayer.cc>
> > ---
> > doc/protocols.texi | 19 +++++++++++++++++++
> > 1 file changed, 19 insertions(+)
> >
> > diff --git a/doc/protocols.texi b/doc/protocols.texi
> > index 05c4bdb..41b43d4 100644
> > --- a/doc/protocols.texi
> > +++ b/doc/protocols.texi
> > @@ -1,3 +1,22 @@
> > +@chapter Protocol Options
> > +@c man begin PROTOCOL OPTIONS
> > +
> > +The libavformat library provides some generic global options, which
> > +can be set on all the protocols. In addition each protocol may support
> > +so-called private options, which are specific for that component.
> > +
> > +The list of supported options follows:
> > +
> > +@table @option
> > +@item protocol_whitelist @var{list} (@emph{input})
> > +"," separated List of allowed protocols. "ALL" matches all protocols.
> > protocols
>
> Nit:
> Set a ","-separated list of allowed protocols. "ALL" matches all protocols.
> Protocols
>
>
> > +prefixed by "-" are disabled.
>
> > The default is that initially all protocols are
>
> This "initially" is confusing.
>
> > +allowed but protocols used by a protocol are restricted to a per protocol
> > +subset.
>
> What about:
>
> All protocols are allowed by default but protocols used by a another
> protocol (nested protocols) are restricted to a per protocol subset.all changed as suggested and applied thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is what and why we do it that matters, not just one of them.
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
