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: Thu, 5 Jan 2017 05:26:25 +1100 [thread overview]
Message-ID: <20170105052625.12fc1a7d@canb.auug.org.au> (raw)
In-Reply-To: <20170104150108.xu3vvt5iz2yf24z2@thunk.org>
Hi Ted,
On Wed, 4 Jan 2017 10:01:08 -0500 Theodore Ts'o <tytso@mit•edu> wrote:
>
> On Wed, Jan 04, 2017 at 10:51:01PM +1100, Stephen Rothwell wrote:
> >
> > Added from tomorrow. Should I add the for-stable branch as well (as a
> > bug fixes tree)?
>
> The master branch should include the for-stable branch 99.9% of the
> time (for my own testing sanity), but if it's not too much trouble,
> sure, that would be great. If it would cause you too much extra work
> on your end, it might not be worth it; I'll leave it up to you.
Added. The bug fix trees all get merged together, so it is no problem
for me to add more.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-01-04 18:26 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
2017-01-04 15:01 ` Theodore Ts'o
2017-01-04 18:26 ` Stephen Rothwell [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=20170105052625.12fc1a7d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tytso@mit$(echo .)edu \
/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