All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Please add fscrypt.git to linux-next
Date: Wed, 4 Jan 2017 22:51:01 +1100	[thread overview]
Message-ID: <20170104225101.209ed782@canb.auug.org.au> (raw)
In-Reply-To: <20170104044424.jcztr7swmyjc2cwn@thunk.org>

Hi Ted,

On Tue, 3 Jan 2017 23:44:24 -0500 Theodore Ts'o <tytso@mit.edu> wrote:
>
> 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.

Added from tomorrow.  Should I add the for-stable branch as well (as a
bug fixes tree)?

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

  reply	other threads:[~2017-01-04 11:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  4:44 Please add fscrypt.git to linux-next Theodore Ts'o
2017-01-04 11:51 ` Stephen Rothwell [this message]
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=20170104225101.209ed782@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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.