[FFmpeg-devel] On in-tree external headers

Timo Rothenpieler timo at rothenpieler.org
Sun Nov 5 22:04:32 EET 2017

Am 05.11.2017 um 19:59 schrieb Mark Thompson:
> On 05/11/17 18:42, Carl Eugen Hoyos wrote:
>> 2017-11-05 19:35 GMT+01:00 Mark Thompson <sw at jkqxz.net>:
>>> On 05/11/17 18:28, Carl Eugen Hoyos wrote:
>>>> 2017-11-05 15:24 GMT+01:00 Mark Thompson <sw at jkqxz.net>:
>>>>> On 30/10/17 19:51, Mark Thompson wrote:
>>>>> "No external headers may be included in the ffmpeg tree."
>>>> So you suggest to remove the Nvidia header?
>>> If that specific policy is adopted then it would have to be.
>> Then I don't think this policy is useful.
>> Iirc, there is a second external header, I have never used
>> either of those but judging from user response, both features
>> are heavily used making a removal a no-go.
> Ok, sure.
> How about:
> "No external headers may be added to the ffmpeg tree, unless they are for AviSynth or Nvidia."

I don't think a strict "no external headers" rule makes sense or is a 
good idea at all. Specially if there are seemingly arbitrary exceptions.

If such a rule is to be added at all, it should list the conditions 
under which external headers can be added. And it should clearly be an 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3994 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20171105/ff772aee/attachment.bin>

More information about the ffmpeg-devel mailing list