From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.15-rc6
Date: Mon, 25 Oct 2021 20:47:55 +0100 [thread overview]
Message-ID: <YXcJ6wQxW72aaGYB@sirena.org.uk> (raw)
In-Reply-To: <CAHk-=whPA5ZgXAG08vqtvZw3DK5H7Tkd9r+ZHSxxNaKYWzjw9g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Mon, Oct 25, 2021 at 11:07:16AM -0700, Linus Torvalds wrote:
> Mark, please stop doing these mindless AND INCORRECT back-merges of my
> tree. There is absolutely no excuse for garbage like this:
Sorry about that. JFTR (and bearing in mind your other points) it looks
like I messed up the first time and then didn't notice that the bad
merge was in my rerere cache the second time, if I am doing these I
should remember to specify --no-rerere-autoupdate so that any mistakes
that do happen are less likely to get repeated.
> If you really need to do a back-merge, explain WHY. And it had better
> be some important reason.
> In particular, the reson should not be "fix conflict", because you're
> clearly not particularly good at it.
A good portion (I'm pretty sure the majority) of the backmerges I do are
due to dependencies for new patches, but obviously you can't tell that
without something in the commit log which like you say should be there
and will be in future.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-10-25 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 6:14 Linus Torvalds
2021-10-19 20:33 ` Guenter Roeck
2021-10-25 18:07 ` Linus Torvalds
2021-10-25 19:47 ` Mark Brown [this message]
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=YXcJ6wQxW72aaGYB@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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
all inboxes | Powered by JetHome®