Russell King writes:
> There are various options here:
>
> 1. Either I can fix up all architectures, and send a patch to this list, or
Fixup all the architectures and send this and the ARM bits to Linus.
I really would wish folks would not choose Alan as the first place
to send the patch. I'm not directly accusing anyone of it, but it
does appear that often AC is used as a "back door" to get a change
in. While this scheme most of the time, often it unnecessarily
overworks Alan which I think is unfair.
Sending it to Linus first also eliminates 2 levels of indirection
each time Linus wants something done differently in the change.
person --> alan --> linus --> needs change
alan BCC's person, person codes new version
person --> alan --> linus --> etc. etc.
Sure Alan could fix it up himself, but...
My main point is that for changes like this, sending stuff to Alan
first is often an ineffective mechanism. If someone were to reply to
this "Linus is hard to push changes too, or takes too long" my reply
is "if this is really the problem, should the burdon should be
entirely placed on Alan's shoulders?"
The AC patches are huge, but they have substantially decreased in size
during the recent 2.4.4-preX series. And sure, Alan makes conscious
decisions to apply patches and eventually work to push them to Linus,
but honestly people should consider ways to help decrease his load.
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 23 2001 - 21:00:44 EST