[Bug time/21716] Crash in glibc's mktime in low-memory situations

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=21716

--- Comment #10 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to eggert from comment #9)
> (In reply to Joseph Myers from comment #8)
> > Note for future commits that if you use Bugzilla with an @gcc.gnu.org
> > address it should give sufficient rights to mark a bug fixed and set the
> > target milestone to the first mainline release in which it was fixed; this
> > should generally be done by the committer.
> 
> Thanks, first I've heard that. I don't have a @gcc.gnu.org email address;
> how do I get one? I visited https://gcc.gnu.org to try to find out, but
> couldn't find anything. Also, should I start making all my glibc
> contributions from a gcc.gnu.org email address, or is it OK to use it only
> for bugzilla maintenance that is off-limits to ordinary users?

We can also grant the necessary privileges to your eggert@cs.ucla.edu account
if that works for you.

--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 19 Sep 2018, eggert at cs dot ucla.edu wrote:

> Thanks, first I've heard that. I don't have a @gcc.gnu.org email address; how
> do I get one? I visited https://gcc.gnu.org to try to find out, but couldn't
> find anything. Also, should I start making all my glibc contributions from a
> gcc.gnu.org email address, or is it OK to use it only for bugzilla maintenance
> that is off-limits to ordinary users?

If you have commit access to any project on sourceware / gcc.gnu.org you 
automatically have an email address there.  See

https://sourceware.org/sourceware/accountinfo.html

for how to update where that forwards to.  It's only necessary to use it 
to get editbugs access for Bugzilla, not for any other contributions.

-- 
You are receiving this mail because:
You are on the CC list for the bug.