All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Theodore Tso <tytso@mit.edu>
Cc: bugme-admin@linux-foundation.org, linux-ext4@vger.kernel.org,
	Sami Liedes <sliedes@cc.hut.fi>,
	Francois Valenduc <francois.valenduc@tvcablenet.be>
Subject: Re: The default assignee for the ext4 component goes nowhere
Date: Sun, 2 Nov 2008 19:32:26 -0800	[thread overview]
Message-ID: <20081102193226.df026896.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081102230806.GN8134@mit.edu>

On Sun, 2 Nov 2008 18:08:06 -0500 Theodore Tso <tytso@mit.edu> wrote:

> On Sun, Nov 02, 2008 at 01:48:03PM -0800, Andrew Morton wrote:
> > 
> > I think the normal way of doing this is to create an account at bugzilla
> > called linux-ext4@vger.kernel.org then you can log in using that account
> > and add it to various assignees using the "users to watch" feature.
> 
> Ah, so the fs_ext4@kernel-bugs.osdl.org is really a bugzilla
> pseudo-user?

I guess so.

>   But for the ext3 component was set to assign bugs to you
> by default, as opposed to creating a fs_ext3 pseudo-user?

Ah.  We'll need to change that.  You don't want all my bugzilla traffic
landing on linux-ext4 :)

> I'm just trying to figure out how the bugzilla system is supposed to
> be working...

I'm far from a definitive source on that matter.

I'm not sure who's reading bugme-admin at present.

  reply	other threads:[~2008-11-03  3:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Kwkhw-0007O5-Mr@closure.thunk.org>
2008-11-02 21:48 ` The default assignee for the ext4 component goes nowhere Andrew Morton
2008-11-02 23:08   ` Theodore Tso
2008-11-03  3:32     ` Andrew Morton [this message]
2008-11-03  7:01       ` Martin Bligh
2008-11-03 13:26         ` Theodore Tso
2008-11-03 15:53           ` Martin Bligh
2008-11-03 16:58         ` Eric Sandeen
2008-11-03 18:23           ` Theodore Tso

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=20081102193226.df026896.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-admin@linux-foundation.org \
    --cc=francois.valenduc@tvcablenet.be \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sliedes@cc.hut.fi \
    --cc=tytso@mit.edu \
    /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.