Lets give a good instance of where a "two minute reply" doesn't work.
Patch 816/1:
http://www.arm.linux.org.uk/developer/patches/?action=viewpatch&id=816/1
Patch received - 30 November. Comment made - 13 December. Reply - 13th
December - "Could you be more detailed on these points".
Well, the comment that's there was written over a couple of hours or more.
Why? Because it had interdependencies on a number of other patches to see
what was going on behind some of the indirections and so forth. That mail
hasn't had a reply yet is:
- its buried behind 200 other messages, so its out of sight.
- it would require me to stop and think about it for significantly
longer to work out what this patch and the other patches were
trying to do.
Oh, don't get me wrong - I'm not about to give up my patch system! It
does serve some very important purposes in making my life easier:
- not loosing patches I want to apply under a mountain of email.
- lets other people find patches that might be useful, but weren't
applied, and see the feedback on the patch.
I'd encourage anyone who wants to follow up this email to go and look
at the patches in question first - probably the easiest way is to go to:
http://www.home.arm.linux.org.uk/developer/patches/
type 'ipaq' into the "search for patch summaries containing" box and hit
enter. Note that most of the ipaq patches remaining depend on 816/1.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
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/