linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
	ebiggers@google.com, mhalcrow@google.com, richard@nod.at,
	linux-ext4@vger.kernel.org, linux-f2fs@vger.kernel.org,
	linux-fscrypt@vger.kernel.org
Subject: Re: Creating a mailing list, git tree, and patchwork project for fscrypt
Date: Wed, 29 Mar 2017 14:14:12 -0700	[thread overview]
Message-ID: <20170329211412.GB29310@gmail.com> (raw)
In-Reply-To: <20161216203732.g65wjf2wgc6rsijy@thunk.org>

On Fri, Dec 16, 2016 at 03:37:32PM -0500, Theodore Ts'o wrote:
> I'm thinking about creating a separate mailing list (linux-fscrypt),
> git tree and patchwork project, just to make it easier to track the
> patches which are coming in.
> 
> Does anyone have any objections with that plan?
> 
> Cheers,
> 

This seems to have done for a while now:
	
    * http://vger.kernel.org/vger-lists.html#linux-fscrypt
    * https://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git/
    * https://patchwork.kernel.org/project/linux-fscrypt/list/

Were you planning to also update the MAINTAINERS file to refer to the new list?

- Eric

      parent reply	other threads:[~2017-03-29 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 20:37 Creating a mailing list, git tree, and patchwork project for fscrypt Theodore Ts'o
2016-12-16 20:39 ` Richard Weinberger
2016-12-16 20:53 ` Eric Biggers
2016-12-16 22:04   ` Theodore Ts'o
2016-12-16 22:25     ` Eric Biggers
2017-03-29 21:14 ` Eric Biggers [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=20170329211412.GB29310@gmail.com \
    --to=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mhalcrow@google.com \
    --cc=richard@nod.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).