From: Jens Axboe <axboe@kernel.dk>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] io_uring changes for 5.9-rc1
Date: Mon, 3 Aug 2020 16:31:19 -0600 [thread overview]
Message-ID: <829a70b8-f1fe-a31b-c380-14c7bb1862b6@kernel.dk> (raw)
In-Reply-To: <20200803211050.ib2km76lch5abnjb@chatter.i7.local>
On 8/3/20 3:10 PM, Konstantin Ryabitsev wrote:
> On Mon, Aug 03, 2020 at 01:53:12PM -0700, Linus Torvalds wrote:
>> On Mon, Aug 3, 2020 at 1:48 PM Linus Torvalds
>> <torvalds@linux-foundation.org> wrote:
>>>
>>> I've pushed out my merge of this thing [..]
>>
>> It seems I'm not the only one unhappy with the pull request.
>>
>> For some reason I also don't see pr-tracker-bot being all happy and
>> excited about it. I wonder why.
>
> My guess it's because the body consists of two text/plain MIME-parts and
> Python returned the merge.txt part first, where we didn't find what we
> were looking for.
>
> I'll see if I can teach it to walk all text/plain parts looking for
> magic git pull strings instead of giving up after the first one.
Thanks, I was a bit puzzled on that one too, and this time it definitely
wasn't because the tag wasn't there.
In terms of attachments, I'm usually a fan of inlining, but seemed cleaner
to me to attach the merge resolution as there's already a ton of other
stuff in that email.
--
Jens Axboe
next prev parent reply other threads:[~2020-08-03 22:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 21:41 [GIT PULL] io_uring changes for 5.9-rc1 Jens Axboe
2020-08-03 20:48 ` Linus Torvalds
2020-08-03 20:53 ` Linus Torvalds
2020-08-03 21:10 ` Konstantin Ryabitsev
2020-08-03 22:31 ` Jens Axboe [this message]
2020-08-03 22:30 ` Jens Axboe
2020-08-03 23:18 ` Jens Axboe
2020-08-03 23:31 ` Jens Axboe
2020-08-03 23:49 ` Linus Torvalds
2020-08-03 23:56 ` Jens Axboe
2020-08-04 0:11 ` Linus Torvalds
2020-08-03 23:34 ` Linus Torvalds
2020-08-03 23:43 ` Jens Axboe
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=829a70b8-f1fe-a31b-c380-14c7bb1862b6@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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).