On 06/07/2010 11:05 PM, Jeff Law wrote: > On 06/07/10 14:31, Ian Lance Taylor wrote: >> The gcc project currently has a problem: when people who are not >> regular gcc developers send in a patch, those patches often get >> dropped. They get dropped because they do not get reviewed, and they >> get dropped because after review they do not get committed. This >> discourages new developers and it means that the gcc project does not >> move as fast as it could. > So perhaps the thing to do is somehow separate patches from regular > contributors and irregular contributors. A relatively easy way to do > this would be for a regular contributor to include a keyword in their > message to gcc-patches to mark the thread as not needing 3rd party > tracking/pings. This makes sense. Thinking out loud myself, even for irregular contributors, the idea of a ping-man doesn't really sound right, it's a boring and error-prone task. Can anybody think of a way to automate the job? For patches corresponding to Bugzilla entries we already have, more or less, a complete procedure in place, I wonder if we could do something for the other contributions...
Paolo.
