On Wed, Nov 23, 2016 at 08:51:16PM +0100, Janne Grunau wrote:
> On 2016-11-23 11:58:38 +0100, Diego Biurrun wrote:
> > On Tue, Nov 22, 2016 at 08:39:26PM +0100, Janne Grunau wrote:
> > > On 2016-11-22 16:43:50 +0100, Diego Biurrun wrote:
> > > > On Mon, Nov 21, 2016 at 12:31:24AM +0100, Janne Grunau wrote:
> > > > > --- a/configure
> > > > > +++ b/configure
> > > > > @@ -348,9 +348,8 @@ Developer options (useful when working on Libav
> > > > > itself):
> > > > > - --ignore-tests=TESTS whitespace-separated list (without
> > > > > "fate-" prefix
> > > > > - in the name) of tests not to run as part
> > > > > of the
> > > > > - fate target
> > > > > + --ignore-tests=TESTS comma-separated list (without "fate-"
> > > > > prefix
> > > > > + in the name) of tests which result is
> > > > > ignored
> > > >
> > > > whose result
> > > >
> > > > Why comma-separated instead of whitespace-separated?
> > >
> > > to be more in line with the other lists configure consumes and I find
> > > whitespace separated lists as configure parameters midly annoying
> >
> > Am I overlooking such a list apart from --{en|dis}able-random?
> > Because that one is a fringe feature that was never used for
> > anything..
>
> yes, all the --{enable,disable}-{encoder,decoder,demuxer,...} options
You're right, let's keep it consistently comma-separated.
Diego
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
