From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Subject: Re: mm.git grew a branch
Date: Wed, 9 Apr 2025 11:02:02 +1000 [thread overview]
Message-ID: <20250409110202.26930e75@canb.auug.org.au> (raw)
In-Reply-To: <20250408173246.5322166aaadc8c91cd8b09bf@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]
Hi Andrew,
On Tue, 8 Apr 2025 17:32:46 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 1 Apr 2025 22:32:31 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > On Tue, 1 Apr 2025 03:04:18 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> > >
> > > Stephen, I've added a new branch to mm.git: "mm-new". It is for
> > > newly-added MM material which may not yet be ready for linux-next
> > > exposure, so please don't include mm-new in linux-next.
> > >
> > > mm-new sits atop mm-unstable. Patches in mm-new will be moved into
> > > mm-unstable as they mature.
> > >
> > > I'll also use mm-new to queue up material during that lazy interval
> > > between "Linus merged our stuff" and "Linus cut -rc1". So you
> > > shouldn't need to kick me out of -next any more ;)
> >
> > Excellent, thanks for letting me know.
>
> um, it appears that mm-new is being included in linux-next's master branch?
I haven't changed anything. I merge your mm-hotfixes-unstable,
mm-stable, mm-nonmm-stable and mm-everything (which used to just
include mm-unstable and mm-nonmm-unstable) branches.
Contact -next name repo remote branch
------- ---------- ---- -------------
Andrew Morton <akpm@linux-foundation.org> mm-hotfixes git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm mm-hotfixes-unstable
Andrew Morton <akpm@linux-foundation.org> mm-stable git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm mm-stable
Andrew Morton <akpm@linux-foundation.org> mm-nonmm-stable git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm mm-nonmm-stable
Andrew Morton <akpm@linux-foundation.org> mm git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm mm-everything
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-09 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 10:04 Andrew Morton
2025-04-01 11:32 ` Stephen Rothwell
2025-04-09 0:32 ` Andrew Morton
2025-04-09 1:02 ` Stephen Rothwell [this message]
2025-04-09 1:55 ` Andrew Morton
2025-04-09 2:14 ` 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=20250409110202.26930e75@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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