All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Martin Bligh <mbligh@google.com>
Cc: bugme-admin@linux-foundation.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bugzilla permissions
Date: Fri, 16 Jan 2009 21:28:29 +0100	[thread overview]
Message-ID: <20090116212829.569f4adb@hyperion.delvare> (raw)
In-Reply-To: <33307c790901160935v2495615fo4ee0998d348fa117@mail.gmail.com>

On Fri, 16 Jan 2009 09:35:45 -0800, Martin Bligh wrote:
> > Dear bugzilla admin,
> 
> Please send bugzilla admin emails to bugme-admin@linux-foundation.org
> (is linked from the front page of http://bugzilla.kernel.org). Sorry, I can't
> keep up with reading all of LKML nowadays ;-)
> 
> > Could you please unlock bugzilla so that everybody (starting with me)
> > is allowed to change the attachment types? I am a bit tired of having
> > to e-mail the person who created the attachment to ask him/her to
> > change the type from application/octet-stream to text/plain so that I
> > can see the attachment directly in my web browser. If we want people to
> > help with bugs, we must make it as easy for them as possible.
> 
> Given that there's no real control on bugzilla accounts, I'm somewhat
> reluctant to make it a complete free for all and let any new user edit
> any bug. However, for anyone running a subsystem, or anyone else
> that I have a vague clue who they are (or any established developer
> will vouch for, anyone I can see git commits for, etc), I am perfectly
> willing to enable global edit on a individual basis. Hasn't been a big
> problem up until now, so I suspect it won't turn into one.
> 
> I enabled your account. Thanks for looking at bugs ;-)

Thanks Martin!

-- 
Jean Delvare

  parent reply	other threads:[~2009-01-16 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 12:27 Bugzilla permissions Jean Delvare
2009-01-16 17:35 ` Martin Bligh
2009-01-16 17:36   ` Martin Bligh
2009-01-16 20:28   ` Jean Delvare [this message]
2009-01-17 11:08   ` Marcin Slusarz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090116212829.569f4adb@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=bugme-admin@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.