Syncing platform-specific bits with generic code (was: Mark inputs being ZERO as unlikely __mul in powerpc)
Siddhesh Poyarekar
siddhesh.poyarekar@gmail.com
Wed Feb 20 17:07:00 GMT 2013
On 20 February 2013 22:24, Carlos O'Donell <carlos@redhat.com> wrote:
>> "All maintainers listed in this file, including the Write After Approval
>> developers, are allowed to check in obvious fixes.
>
> I'm confused. Our MAINTAINER's page already says that?
>
> "Write after Consensus and/or approval from machine maintainer..."
>
> Where Consensus is a link to the Consensus page.
Not our MAINTAINERS page, it's the gdb MAINTAINERS file. Also, not
just that line, the entire block I put in double quotes. See the
"Obvious Fix Rule" here:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/MAINTAINERS?rev=1.503&content-type=text/x-cvsweb-markup&cvsroot=src&only_with_tag=MAIN
> If something is missing form the Consensus page then we need to gather
> consensus and add it?
I was proposing instead that we allow maintainers to use their
judgement in considering what is obvious and reviewers give feedback
if a commit was not 'obvious' and ought to have been discussed since
there is a possibility of disagreement. Based on this, we can put in
*exclusions* to the obvious commit rule rather than inclusions.
--
http://siddhesh.in
More information about the Libc-alpha
mailing list