On 2017-12-05 02:07, Timothy Gu wrote:
Hi,
[...]
As the Documentation maintainer, this patch LGTM. With community consensus,
this is thusly applied.
Thanks to you all.
Timothy
Thank you, Timothy, and everyone who participated in this discussion.
The end product is a small change to the do
Hi,
On Mon, Dec 4, 2017 at 4:43 AM Carl Eugen Hoyos wrote:
> The patch is not ok, Carl Eugen
It is clear that you have no respect for community consensus.
9 for removal of mandatory status (10 counting myself):
TR: http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2017-November/220272.html
PBM:
On 12/4/17, Carl Eugen Hoyos wrote:
> 2017-12-04 8:09 GMT+01:00 Jim DeLaHunt :
>
>> @section Documentation/Other
>> +@subheading Subscribe to the ffmpeg-devel mailing list.
>> +It is important to be subscribed to the
>> +@uref{https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel,
>> ffmpeg-deve
2017-12-04 8:09 GMT+01:00 Jim DeLaHunt :
> @section Documentation/Other
> +@subheading Subscribe to the ffmpeg-devel mailing list.
> +It is important to be subscribed to the
> +@uref{https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel, ffmpeg-devel}
> +mailing list. Almost any non-trivial patc
The Developer Documentation had instructions to
subscribe to the ffmpeg-cvslog email list. But that is
no longer accurate. For the purposes in this section --
review of patches, discussion of development issues --
ffmpeg_devel is the appropriate email list. Some developers
may want to monitor ffmpe
