[FFmpeg-devel] [PATCH] Add detail to the documentation for ffmpeg -map.
Sat Mar 12 12:40:53 CET 2011
On 03/12/2011 11:24 AM, Stefano Sabatini wrote:
> Rule of thumb: *public* API changes affect all developers and are
> usually delicate (in subtle ways), so should be mandatory to give a
> reasonable amount of time to people for commenting. Documentation
> patches are not that important, since they can be easily changed later
> and they don't affect (directly) the code.
Documentation patches are relatively low priority coding wise (no direct
effect) but misleading documentation is as annoying as subtly broken
> In general, if there is no one around which has
> time/competence/interest for reviewing a patch this shouldn't prevent
> the commit. Adopting the wait-three-days-and-apply-if-no-comment
> protocol was a good way to ensure that an interested developer can
> still push her changes even in this case. Pinging, updating and
> tracking a patch can be tedious and frustrating.
three-days-and-apply is the same as rushing patches in, with even less
eyes reading it =|
More information about the ffmpeg-devel