From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Petr Mladek <pmladek@suse•com>
Cc: Jiri Kosina <jikos@kernel•org>,
Josh Poimboeuf <jpoimboe@kernel•org>,
Miroslav Benes <mbenes@suse•cz>,
Joe Lawrence <joe.lawrence@redhat•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: please clean up the livepatching tree
Date: Tue, 19 Aug 2025 00:00:07 +1000 [thread overview]
Message-ID: <20250819000007.7cf7b8d9@canb.auug.org.au> (raw)
In-Reply-To: <aKMBV6LfqCYw1wQm@pathway.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Hi Petr,
On Mon, 18 Aug 2025 12:32:55 +0200 Petr Mladek <pmladek@suse•com> wrote:
>
> Just to be sure. What is exactly the problem, the merge commits or
> that it has not been updated since March, please?
The merge commits. Everyday linux-next contained those 70 merges that
added nothing except to complicate the history.
I don't start looking to drop branches from linux-next until they have
not been updated for over a year.
> I have just removed the merge commits.
Thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-08-18 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:14 linux-next: please clean up the livepatching tree Stephen Rothwell
2025-08-18 10:32 ` Petr Mladek
2025-08-18 14:00 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-02 23:31 Stephen Rothwell
2016-08-02 23:41 ` Jiri Kosina
2016-08-03 1:23 ` Stephen Rothwell
2016-08-03 9:29 ` Jiri Kosina
2016-08-05 7:08 ` Takashi Iwai
2016-08-05 13:11 ` Jiri Kosina
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=20250819000007.7cf7b8d9@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jikos@kernel$(echo .)org \
--cc=joe.lawrence@redhat$(echo .)com \
--cc=jpoimboe@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mbenes@suse$(echo .)cz \
--cc=pmladek@suse$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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