From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michal Simek <monstr@monstr.eu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/microblaze patches for 5.6-rc1
Date: Tue, 4 Feb 2020 22:04:25 +0000 [thread overview]
Message-ID: <CAHk-=wj1xRXSKMPt-y=A6-nUqDQQwK2eHHfF96zdk0bWkfUCzQ@mail.gmail.com> (raw)
In-Reply-To: <f2b951c9-f904-58d7-0634-0a0d42f71066@monstr.eu>
On Tue, Feb 4, 2020 at 5:37 PM Michal Simek <monstr@monstr.eu> wrote:
>
> Sorry about it. All that patches has been sent and done till the mid of
> January. Some of them even earlier.
> I just needed to remove one patch from queue which we found is causing
> the issue. That's why instead of revert I completely remove it and
> rebase the rest of the tree.
> I will handle that differently next time.
Note that if this happens again, and you have a really good reason to
rebase, please _mention_ that reason.
The whole taking me by surprise when I notice after-the-fact that I've
pulled something that was committed just hours before is about the
worst thing that can happen (always excepting obviously untested code
- me finding that the code doesn't even compile is even worse, of
course, even if it wasn't recently committed).
So if there's a good reason why something is very recent, and you
mention it, and it's not a common pattern, I get much less upset.
Linus
next prev parent reply other threads:[~2020-02-04 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 11:08 [GIT PULL] arch/microblaze patches for 5.6-rc1 Michal Simek
2020-02-04 13:22 ` Linus Torvalds
2020-02-04 17:37 ` Michal Simek
2020-02-04 22:04 ` Linus Torvalds [this message]
2020-02-04 13:25 ` 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-=wj1xRXSKMPt-y=A6-nUqDQQwK2eHHfF96zdk0bWkfUCzQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
/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).