All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Martin Bligh <mbligh@mbligh.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	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: Mon, 3 Nov 2008 13:23:00 -0500	[thread overview]
Message-ID: <20081103182300.GF29102@mit.edu> (raw)
In-Reply-To: <490F2DC4.9010909@redhat.com>

On Mon, Nov 03, 2008 at 10:58:44AM -0600, Eric Sandeen wrote:
> Martin Bligh wrote:
> > A (very) few people have requested mailing lists get cc'ed on some
> > categories, for which we've set up mailing list users, and had them
> > watch the categories too.
> 
> I think this makes sense for ext4 (I think xfs was one of those few;
> bugs go to xfs-masters@oss.sgi.com for that category IIRC) so at least
> people see them.
> 
> Would anyone on linux-ext4 disagree with setting up the list to watch
> the ext3 & ext4 categories?

On the theory that it is easier to ask forgiveness than to get
permission :-), I've subscribed linux-ext4@vger.ekernel org to the
ext2, ext3, and ext4 categories.  If this result in too much e-mail,
folks can complain and we can cut things back.

						- Ted

      reply	other threads:[~2008-11-03 18:23 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
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 [this message]

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