[FFmpeg-devel] [PATCH v2] libavutil: add an FFT & MDCT implementation

Carl Eugen Hoyos ceffmpeg at gmail.com
Sun May 12 01:08:20 EEST 2019


Am Sa., 11. Mai 2019 um 14:41 Uhr schrieb Lynne <dev at lynne.ee>:
>
> May 10, 2019, 8:59 PM by ceffmpeg at gmail.com:
>
> > Am Fr., 10. Mai 2019 um 19:54 Uhr schrieb Lynne <> dev at lynne.ee <mailto:dev at lynne.ee>> >:
> >
> >>
> >> May 10, 2019, 4:14 PM by >> dev at lynne.ee <mailto:dev at lynne.ee>>> :
> >>
> >> > Patch updated again.
> >> > Made some more cleanups to the transforms, the tables and the main context.
> >> > API changed again, now the init function populates the function pointer for transform.
> >> > I decided that having a separate function would encourage bad usage (e.g. calling
> >> > the function every time before doing a transform rather than storing the pointer) when
> >> > we're trying to avoid the overhead of function calls.
> >> > Also adjusted file names to match the API.
> >> >
> >>
> >> Forgot to change an include, new patch attached.
> >>
> >
> > If I understand the commit message correctly, some of the code
> > in the new file you are adding comes from other parts of FFmpeg.
> > I am surprised that there is no copyright claim on the top of this
> > new file.
> > Is there none on top of the files you took the code from?
> >
>
> The project isn't consistent with updating nor putting copyright headers on files so
> I'd rather keep the headers clean. Commit messages and authors are the only way to
> know who authored what.

I don't think this is correct, but that is not the question: Copyright
law is (at least here)
very clear, if somebody put his name on top of the file, you must not remove it,
especially not when moving code from one file into another.

> I could credit the authors fully in the commit message, then authorship can still be
> tracked and the headers will be clean.

There is nothing wrong with putting the authors in the commit message, this can
not replace the notice on top of the files though.

This of course only applies if there is such a notice in existing
files from which
you move or copy code.

Carl Eugen


More information about the ffmpeg-devel mailing list