From: Konstantin Khlebnikov <koct9i@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: broonie@kernel.org, linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, linux-next@vger.kernel.org,
Michal Hocko <mhocko@suse.cz>,
mm-commits@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: mmotm 2019-10-18-22-40 uploaded
Date: Sat, 19 Oct 2019 20:47:52 +0300 [thread overview]
Message-ID: <CALYGNiNVJ6WZwDETrq4X4oaPBOx7wC89Gh8-ZOScY_Bf8H5Mdw@mail.gmail.com> (raw)
In-Reply-To: <20191019054039.vsWMD_v7t%akpm@linux-foundation.org>
On Sat, Oct 19, 2019 at 8:40 AM <akpm@linux-foundation.org> wrote:
>
> The mm-of-the-moment snapshot 2019-10-18-22-40 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
>
> This tree is partially included in linux-next. To see which patches are
> included in linux-next, consult the `series' file. Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
>
>
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release. Individual mmotm releases are tagged. The master branch always
> points to the latest release, so it's constantly rebasing.
>
> http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
I seems git mirror does not update anymore.
Latest tag is v5.3-rc7-mmots-2019-09-03-21-33
prev parent reply other threads:[~2019-10-19 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 5:40 mmotm 2019-10-18-22-40 uploaded akpm
2019-10-19 15:45 ` mmotm 2019-10-18-22-40 uploaded (i915) Randy Dunlap
2019-10-19 15:59 ` mmotm 2019-10-18-22-40 uploaded (mm/vmstat.c) Randy Dunlap
2019-10-19 17:47 ` Konstantin Khlebnikov [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=CALYGNiNVJ6WZwDETrq4X4oaPBOx7wC89Gh8-ZOScY_Bf8H5Mdw@mail.gmail.com \
--to=koct9i@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).