From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the slab tree
Date: Mon, 9 Sep 2024 09:11:34 -0400 [thread overview]
Message-ID: <20240909-nice-important-mink-2fac60@lemur> (raw)
In-Reply-To: <5661a983-9875-4cdb-8bdb-fc83e82f0b58@suse.cz>
On Mon, Sep 09, 2024 at 11:40:25AM GMT, Vlastimil Babka wrote:
> > Hm, that's very odd that the IDs changed. The only thing that I did was
> > b4 trailers -u on the branch to quickly check whether I missed an RvBs
> > or Acks. But there were none so I assumed that the commit ids wouldn't
>
> I guess b4 could be smarter and not perform/rollback the history rewrite if
> there's nothing to change.
That should be already the case. If there were no updates to commits, then it
should have been a no-op, so I'm pretty sure something else must have
happened.
-K
next prev parent reply other threads:[~2024-09-09 13:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:12 linux-next: duplicate patches in the slab tree Stephen Rothwell
2024-09-09 7:18 ` Vlastimil Babka
2024-09-09 9:16 ` Christian Brauner
2024-09-09 9:40 ` Vlastimil Babka
2024-09-09 10:13 ` Christian Brauner
2024-09-09 10:35 ` Vlastimil Babka
2024-09-09 10:42 ` Christian Brauner
2024-09-09 11:02 ` Christian Brauner
2024-09-09 11:45 ` Stephen Rothwell
2024-09-09 12:19 ` Christian Brauner
2024-09-09 12:37 ` Christian Brauner
2024-09-09 13:44 ` Stephen Rothwell
2024-09-09 12:09 ` Vlastimil Babka
2024-09-09 12:18 ` Christian Brauner
2024-09-09 13:11 ` Konstantin Ryabitsev [this message]
2024-09-09 8:10 ` Stephen Rothwell
2024-09-09 8:32 ` Vlastimil Babka
2024-09-09 8:49 ` Vlastimil Babka
2024-09-09 9:33 ` Stephen Rothwell
2024-09-09 9:28 ` Stephen Rothwell
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=20240909-nice-important-mink-2fac60@lemur \
--to=konstantin@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vbabka@suse.cz \
/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