From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] XArray for 4.19
Date: Wed, 22 Aug 2018 11:23:38 -0700 [thread overview]
Message-ID: <20180822182338.GA19458@bombadil.infradead.org> (raw)
In-Reply-To: <CA+55aFw+dwofadgvzrM-UCMSih+f1choCwW+xFFM3aPjoRQX_g@mail.gmail.com>
On Tue, Aug 21, 2018 at 08:00:18PM -0700, Linus Torvalds wrote:
> On Tue, Aug 21, 2018 at 7:50 PM Matthew Wilcox <willy@infradead.org> wrote:
> > So, should I have based just on your tree and sent you a description of
> > what a resolved conflict should look like?
>
> Absolutely.
>
> Or preferably not rebasing at all, just starting from a good solid
> base for new development in the first place.
Ah, I remember now, it was more complex than a textual conflict.
Dan added an entirely new function here:
http://git.infradead.org/users/willy/linux-dax.git/commitdiff/c2a7d2a115525d3501d38e23d24875a79a07e15e
which needed to be converted to XArray. So I should have pulled in his
branch as a merge somewhere close to the end of my series, then done a
fresh patch on top of that to convert it?
It would have been pretty ugly because he modified a function I deleted.
I might try it out just to show how bad it would have been.
next prev parent reply other threads:[~2018-08-22 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 16:13 [GIT PULL] XArray for 4.19 Matthew Wilcox
2018-08-22 2:09 ` Linus Torvalds
2018-08-22 2:50 ` Matthew Wilcox
2018-08-22 3:00 ` Linus Torvalds
2018-08-22 18:23 ` Matthew Wilcox [this message]
2018-08-22 18:41 ` Linus Torvalds
2018-08-24 5:25 ` Stephen Rothwell
2018-08-22 17:40 ` Christopher Lameter
2018-08-22 17:43 ` Linus Torvalds
2018-08-22 18:23 ` Dan Williams
2018-08-24 13:21 ` Vlastimil Babka
2018-08-24 14:12 ` Christopher Lameter
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=20180822182338.GA19458@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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).