Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/hls, dashdec: Don't use AV_OPT_FLAG_* in av_dict_set()
Date: Sun, 15 May 2022 20:51:21 +0200
Message-ID: <DB6PR0101MB2214754DA8E7F225DEA71C518FCC9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CAEu79SZyo0XU8S+2X-ymkqym8_24Vb2zXCKX8rLoxDcPsHiWGQ@mail.gmail.com>

Jan Ekström:
> On Sun, May 15, 2022 at 8:57 PM Andreas Rheinhardt
> <andreas.rheinhardt@outlook.com> wrote:
>>
>> av_dict_set() expects a different set of flags, namely the AV_DICT_*
>> flags. Using AV_OPT_FLAG_DECODING_PARAM (or any AV_OPT_FLAG_*) ic
>> av_dict_set() is therefore completely wrong and given that av_dict_set()
>> just doesn't care about whether the string it receives has anything
>> to do with a decoding parameter or not, it should just be removed
>> without replacement.
>> (The numerical value of AV_OPT_FLAG_DECODING_PARAM currently coincides
>> with AV_DICT_IGNORE_SUFFIX. Given that the dictionaries we are dealing
>> with here are always empty (i.e. NULL) before the calls to
>> av_dict_set(), this flag changes nothing. It would be different if
>> it were equal to one of the AV_DICT_DONT_STRDUP_* values.)
> 
> LGTM as far as the patch contents go. Well noticed.
> 
> For commit message I think we utilize do not utilize capital letters
> after the "prefix: ". This can be changed as you apply the patch :) .
> 

"we"? I always use capital letters here; so does Michael Niedermayer
(mostly). In the last two years, 4679 patches used a capital letter
after the ':', whereas 4409 used a non-capital letter. Granted, 3286 of
the 4679 are from me, but I don't think we have a policy here. Neither
should we.

> Personally I would have worded it a la "don't use AV_OPT flags with
> av_dict_set()", but this is just a preference and you are free to
> ignore this bit.

And I thought I wrote it in that way.

- Andreas
_______________________________________________
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".

  reply	other threads:[~2022-05-15 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 17:56 Andreas Rheinhardt
2022-05-15 18:41 ` Jan Ekström
2022-05-15 18:51   ` Andreas Rheinhardt [this message]
2022-05-15 19:21     ` Jan Ekström

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=DB6PR0101MB2214754DA8E7F225DEA71C518FCC9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
    --to=andreas.rheinhardt@outlook.com \
    --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