public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit•edu>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Please add fscrypt.git to linux-next
Date: Tue, 3 Jan 2017 23:44:24 -0500	[thread overview]
Message-ID: <20170104044424.jcztr7swmyjc2cwn@thunk.org> (raw)

Could you please add:

git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git  master

To the linux-next tree?  I was previously feeding fscrypt changes by
merging them into the ext4.git dev branch, but it will make life
simpler if we have a separate git tree for it.

Linus has already accepted a pull request from the for-stable branch
of fscrypt.git.  I plan to send a separate pull request for the master
branch of fscrypt.git during the next merge window.

Thanks!!

						- Ted

             reply	other threads:[~2017-01-04  5:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  4:44 Theodore Ts'o [this message]
2017-01-04 11:51 ` Please add fscrypt.git to linux-next Stephen Rothwell
2017-01-04 15:01   ` Theodore Ts'o
2017-01-04 18:26     ` Stephen Rothwell

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=20170104044424.jcztr7swmyjc2cwn@thunk.org \
    --to=tytso@mit$(echo .)edu \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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