[PATCH v4] Ensure mktime sets errno on error (bug 23789)
Joseph Myers
joseph@codesourcery.com
Fri Nov 2 16:49:00 GMT 2018
On Fri, 2 Nov 2018, Albert ARIBAUD wrote:
> What should I do regarding Bugzilla itself?
https://sourceware.org/glibc/wiki/Bugzilla%20Procedures
https://sourceware.org/glibc/wiki/Committer%20checklist#Update_Bugzilla
The general expectation is that *once a fix has been committed and pushed
to master*, the bug should be marked as RESOLVED/FIXED with the target
milestone set to the next mainline release with the fix. It is the
committer's responsibility to do that update promptly after committing.
Committers have @gcc.gnu.org / @sourceware.org addresses and a Bugzilla
account with such an address should automatically have the required
permissions to update milestones. (Milestones should not be set on open
bugs. If a fix needs to be reverted for some reason, the bug should be
reopened and the milestone setting removed.)
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Libc-alpha
mailing list