This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH v4] Ensure mktime sets errno on error (bug 23789)
- From: Albert ARIBAUD <albert dot aribaud at 3adev dot fr>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Sat, 3 Nov 2018 01:01:18 +0100
- Subject: Re: [PATCH v4] Ensure mktime sets errno on error (bug 23789)
- References: <email@example.com> <20181031165602.697c476f@athena> <20181102070702.27c64d79@athena> <alpine.DEB.firstname.lastname@example.org>
On Fri, 2 Nov 2018 16:48:25 +0000, Joseph Myers
<email@example.com> wrote :
> On Fri, 2 Nov 2018, Albert ARIBAUD wrote:
> > What should I do regarding Bugzilla itself?
> 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.)
I don't have an @gcc.gnu.org or @sourceware.org address; I use my
This means I cannot update Bugzilla properly unless my account gets
given the required permissions, right?