May 13, 2019, 9:53 AM by one...@gmail.com: > On 5/13/19, Carl Eugen Hoyos <> ceffm...@gmail.com > <mailto:ceffm...@gmail.com>> > wrote: > >> Am Mo., 13. Mai 2019 um 00:55 Uhr schrieb James Almer <>> jamr...@gmail.com >> <mailto:jamr...@gmail.com>>> >: >> >>> >>> On 5/12/2019 7:42 PM, Carl Eugen Hoyos wrote: >>> > Am So., 12. Mai 2019 um 23:58 Uhr schrieb Lynne <>>> d...@lynne.ee >>> > <mailto:d...@lynne.ee>>>> >: >>> >> I need *technical* feedback about the API. >>> > >>> > I understand that. >>> >>> Then, if you can't provide technical feedback, please stop replying >>> to this thread (After you provide the source Hendrik requested). >>> >> >> Could you please stop this? >> >> It doesn't matter where you live, and it doesn't matter which license >> you use, you are not allowed to remove a copyright statement that >> was put on top of a source file. >> >> It is arguably not always as clear as in this case, but since it was >> explained where the code comes from, there is really no question >> about this. >> > > Do we need yet another voting for this one? >
Please do, then this thread can be left alone and I can get some actual feedback. I'll ignore Carl's messages for now as I agree with the others that authorship is always preserved through git history. If he disagrees then it becomes a project-wide issue as copyright headers have sometimes not been preserved through refactoring. I can give examples _in_another_thread_. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
