[FFmpeg-devel] [PATCH] Check for bugged make
Thu Oct 30 22:06:31 CET 2008
M?ns Rullg?rd wrote:
> Stefano Sabatini <stefano.sabatini-lala at poste.it> writes:
>> I'll apply at the end of the next weekend if I hear no objections.
> You will do no such thing. I have already said that any changes to
> the build system need my explicit approval. Please cease making
> these threats. I find it quite unfriendly.
I find it a little bewildering (and possibly somewhat unfriendly) that
you interpret these as threats. They have been standard-use boilerplate
the entire time I've been watching MPlayer and FFmpeg development, and
are an apparently highly useful - perhaps even indispensable - tool for
avoiding having patches lie there indefinitely neither approved nor
rejected; I seem to recall that they have led to the takeover of
maintainership (when a previous maintainer had left without fanfare) on
at least one occasion. You are the first person I remember having seen
treat them as at all unusual, and I do not recall having seen any hint
of your doing so until very recently.
Why do you find them objectionable - particularly given that it's very
easy to say "no" in any given case - much less consider them
threatening? Why did you not do so before?
How would you recommend A: ensuring that patches which have been
submitted and received no response are not ignored, and B: not leaving
submitters of such patches in limbo with no idea about whether or not
their patch has even been looked at? Simply pinging is not effective in
all cases; treating a long enough lack of reaction as unanimous consent,
with an advance warning such as this one that that is what is being
done, does seem to be enough. (There are arguments against it in many
cases, of course, but I don't see how they're enough to justify a
blanket ban on the practice...)
Warning: Simply because I argue an issue does not mean I agree with any
side of it.
Secrecy is the beginning of tyranny.
More information about the ffmpeg-devel