seeing as how i have commit access to the gcc tree, could i have
my bugzilla privs extended as well ? atm i only have normal ones
which means i only get to edit my own bugs ... can't dupe/update
other ones people have filed. couldn't seem to find docs for how
to request this, so spamming this lis
On 2016.01.02 at 03:49 -0500, Mike Frysinger wrote:
> seeing as how i have commit access to the gcc tree, could i have
> my bugzilla privs extended as well ? atm i only have normal ones
> which means i only get to edit my own bugs ... can't dupe/update
> other ones people have filed. couldn't see
On Sat, 2 Jan 2016, Mike Frysinger wrote:
seeing as how i have commit access to the gcc tree, could i have
my bugzilla privs extended as well ? atm i only have normal ones
which means i only get to edit my own bugs ... can't dupe/update
other ones people have filed. couldn't seem to find docs
On 31 December 2015 at 18:49, James Dennett wrote:
> On Thu, Dec 31, 2015 at 4:42 AM, Jonathan Wakely
> wrote:
>>
>> On 31 December 2015 at 11:54, Dominik Vogt wrote:
>> > Is there a requirement for a certain minimum Glibc version for
>> > this to work?
>>
>> It doesn't work with any glibc, becau
On 02 Jan 2016 09:53, Marc Glisse wrote:
> On Sat, 2 Jan 2016, Mike Frysinger wrote:
> > seeing as how i have commit access to the gcc tree, could i have
> > my bugzilla privs extended as well ? atm i only have normal ones
> > which means i only get to edit my own bugs ... can't dupe/update
> > ot
On 2 January 2016 at 14:04, Mike Frysinger wrote:
> i completely forgot i had that e-mail address :). i thought i remembered
> seeing people make changes w/out @gcc.gnu.org accounts, but perhaps i'm
> misremembering.
Bug reporters can make certain changes to their own bugs without a
gcc.gnu.org a
