public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Eric Biggers <ebiggers3@gmail.com>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	linux-fscrypt@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
	linux-f2fs-devel@lists.sourceforge.net,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: fscrypt: update mailing list, patchwork, and git
Date: Sun, 30 Apr 2017 02:23:48 -0400	[thread overview]
Message-ID: <20170430062348.7qzgd77edeir4iuk@thunk.org> (raw)
In-Reply-To: <CAOQ4uxgzVOqNXX1DBG8gtYf+81Crkwwi5_kQK=zCVcjiHK7+fg@mail.gmail.com>

On Fri, Apr 28, 2017 at 08:47:41AM +0300, Amir Goldstein wrote:
> 
> Does the fscrypt mailing list allow posting for non-subscribers?
> It is often a nuisance for a passing by developer to subscribe to a mailing list
> just to report a bug or CC a relevant patch.

As far as I know, all of the vger.kernel.org lists allow
non-subscribers to post.

       	   		   	       		       - Ted

  reply	other threads:[~2017-04-30  6:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 23:43 [PATCH] MAINTAINERS: fscrypt: update mailing list, patchwork, and git Eric Biggers
2017-04-27  7:37 ` Richard Weinberger
2017-04-27 17:45   ` Eric Biggers
2017-04-27 19:12     ` Richard Weinberger
2017-04-28  5:47     ` Amir Goldstein
2017-04-30  6:23       ` Theodore Ts'o [this message]
2017-04-30  6:24 ` Theodore Ts'o

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=20170430062348.7qzgd77edeir4iuk@thunk.org \
    --to=tytso@mit.edu \
    --cc=amir73il@gmail.com \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox