Johan Rydberg <[EMAIL PROTECTED]> writes: Hi,
> In other projects that I've worked on, we've used a system where the > core developers can either give a +1 or a -1 on a contributed patch. > If a patch receives two +1's or more, it is accepted (if there are no > -1's) and committed by one of the developers. Interesting, I like this idea. > This is in no way an attempt to overrun any of our maintainers, it is > just an attempt to make things go a bit smoother and faster in the > times when the maintainers are busy with other things. :-) Although I am a maintainer, I do not know some parts of the code as well as some regular contributors do. I do not feel overrun at all. Actually, this will help me evaluate patches I have no clue about. For example, take your latest patch regarding the build system. It looks sane to me, but I have no idea at all if it is acceptable or not. If I do know about a patch, I hope people remind me often enough to have a look, in case I missed a patch in the past. -- Marco _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
