From: Linus Torvalds <torvalds@linux-foundation.org>
To: Christian Brauner <christian@brauner.io>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] clone3 for v5.3
Date: Thu, 11 Jul 2019 10:07:20 -0700 [thread overview]
Message-ID: <CAHk-=wincfPnFxQyiFDJLpNH3gNfUgabeAygN6D3dKXHHaqqjg@mail.gmail.com> (raw)
In-Reply-To: <20190711134552.jvahfwhvaxykbgfl@brauner.io>
On Thu, Jul 11, 2019 at 6:45 AM Christian Brauner <christian@brauner.io> wrote:
>
> Just in case you prefer pulling from a __rebased__ tree. I prepared one.
No, I'd much rather just resolve the conflict. I just wanted to know
what the deal was with the number confusion.
I'll make it use 435, we can sort out openat2 and close_range() when
those happen.
Linus
next prev parent reply other threads:[~2019-07-11 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 15:00 [GIT PULL] clone3 for v5.3 Christian Brauner
2019-07-11 5:24 ` Linus Torvalds
2019-07-11 5:34 ` Christian Brauner
2019-07-11 13:45 ` Christian Brauner
2019-07-11 17:07 ` Linus Torvalds [this message]
2019-07-11 18:35 ` pr-tracker-bot
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='CAHk-=wincfPnFxQyiFDJLpNH3gNfUgabeAygN6D3dKXHHaqqjg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=christian@brauner.io \
--cc=linux-kernel@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).