No bug or public post for commit bc680b336971305cb39896b30d72dc7101b62242

[Joseph Myers]

On Mon, 27 Aug 2018, Carlos O'Donell wrote:

> Regarding bugs, they identify defects and provide downstream with an
> audit trail, but if you didn't fix a glibc bug then you don't need
> one.

That is: if you didn't fix a bug *that was user-visible in a release*.  
There's no need to file a bug if you discover and fix some issue in the 
same development cycle in which it was introduced (if you discover it but 
don't quickly fix it, you should file the bug to make sure it doesn't get 
lost).

-- 
Joseph S. Myers
joseph@codesourcery.com