From: Andreas Larsson <andreas@gaisler.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: David Miller <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] sparc updates for v7.4
Date: Fri, 30 Oct 2026 08:25:47 +0100 [thread overview]
Message-ID: <b8d8f8d6-936c-4a00-a2dc-ac820afd7c7c@gaisler.com> (raw)
In-Reply-To: <CAHk-=wiXTPC_jJ9o7k2JGVwA=F5_JFt4ikY2J4E69xJqYtAFGg@mail.gmail.com>
On 2026-10-29 23:49, Linus Torvalds wrote:
> No. The fix is to NOT REBASE POINTLESSLY.
>
> And no, adding a "tested-by" is simply not a good enough reason to
> rebase long after-the-fact.
Understood. This was my mistake. I was trying to do the right thing and
clearly did not. Sorry about that.
Just to be clear, the followup pull request for sparc-for-7.4-tag2 I did
in this thread is for what has actually been in linux-next. Each commit
there was pushed to my for-next the same day as I committed it.
> And if you have a *major* and actual real reason to rebase (completely
> broken history that needs to be fixed), it should be mentioned and
> explained.
Understood. Sorry for the mess.
Best regards,
Andreas
prev parent reply other threads:[~2026-10-30 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 13:44 Andreas Larsson
2026-10-28 17:03 ` Linus Torvalds
2026-10-28 20:50 ` John Paul Adrian Glaubitz
2026-10-28 20:56 ` John Paul Adrian Glaubitz
2026-10-29 7:03 ` Andreas Larsson
2026-10-29 8:05 ` John Paul Adrian Glaubitz
2026-10-29 9:50 ` Andreas Larsson
2026-10-29 22:49 ` Linus Torvalds
2026-10-30 6:47 ` John Paul Adrian Glaubitz
2026-10-30 7:25 ` Andreas Larsson [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=b8d8f8d6-936c-4a00-a2dc-ac820afd7c7c@gaisler.com \
--to=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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
all inboxes | Powered by JetHome®