glibc AI policy

Joseph Myers josmyers@redhat.com
Thu Apr 2 16:27:38 GMT 2026


On Thu, 2 Apr 2026, Paul Eggert wrote:

>   2) As a submitter, you assert that you have reviewed such code that you
> submit.

I'd say the submitter needs to *understand* the code they are submitting, 
and to *communicate that understanding* with a high-quality commit message 
(and be ready to engage in the review discussion and revise the changes or 
commit message as needed).

Some five-line changes have straightforward local explanations and don't 
need particularly in-depth understanding (provided they are accompanied by 
a test that fails before and passes after the change, if it's supposed to 
be doing something user-visible).  Others deserve much more involved 
explanations (including why the fix belongs in a particular place in the 
code and not in a different place, for example).

-- 
Joseph S. Myers
josmyers@redhat.com



More information about the Libc-alpha mailing list