From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Adding some trees to linux-next?
Date: Tue, 2 Jul 2019 01:42:10 +1000 [thread overview]
Message-ID: <20190702014210.1c95f9f1@canb.auug.org.au> (raw)
In-Reply-To: <20190701153552.GJ1404256@magnolia>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Hi Darrick,
On Mon, 1 Jul 2019 08:35:52 -0700 "Darrick J. Wong" <darrick.wong@oracle.com> wrote:
>
> Could you add my iomap-for-next and vfs-for-next branches to linux-next,
> please? They can be found here:
>
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git#iomap-for-next
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git#vfs-for-next
>
> I've decided that trying to munge all that through the xfs for-next
> branch is too much insanity and splitting them up will help me prevent
> my head from falling off.
Just out of interest, do you intend to send these directly to Linus, or
via another tree?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-01 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 1:06 linux-next: manual merge of the xfs tree with the f2fs tree Stephen Rothwell
2019-07-01 15:35 ` Adding some trees to linux-next? Darrick J. Wong
2019-07-01 15:42 ` Stephen Rothwell [this message]
2019-07-01 15:49 ` Darrick J. Wong
2019-07-01 15:49 ` Stephen Rothwell
2019-07-01 16:31 ` linux-next: manual merge of the xfs tree with the f2fs tree Eric Biggers
2019-07-01 16:47 ` Darrick J. Wong
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=20190702014210.1c95f9f1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=darrick.wong@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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).