From: Michal Hocko <mhocko@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: akpm@linux-foundation.org, broonie@kernel.org,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org
Subject: Re: mmotm 2018-12-21-15-28 uploaded
Date: Mon, 7 Jan 2019 10:23:56 +0100 [thread overview]
Message-ID: <20190107092356.GB31793@dhcp22.suse.cz> (raw)
In-Reply-To: <451ec03f-d669-fcd0-11c7-f7fef9f85a56@arm.com>
On Mon 07-01-19 14:46:43, Anshuman Khandual wrote:
>
>
> On 01/07/2019 02:13 PM, Michal Hocko wrote:
> > Hi,
> >
> > On Mon 07-01-19 13:02:31, Anshuman Khandual wrote:
> >> On 12/22/2018 04:58 AM, akpm@linux-foundation.org wrote:
> > [...]
> >>> A git tree which contains the memory management portion of this tree is
> >>> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.gi
> >>
> >> Hello Michal,
> >>
> >> I dont see the newer tags on this tree. Tried fetching all the tags from the tree
> >> but only see these right now for 2018. This release should have an equivalent tag
> >> (mmotm-2018-12-21-15-28) right ?
> >
> > I have stopped tracking mmotm trees in this tree quite some time ago. I
> > would much rather turn mmotm into a proper git tree which I was
> > discussing with Andrew but we didn't land in anything so far. I hope to
> > use LSFMM this year to resurrect the idea.
> >
>
> Even this tree http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/ does not clone. So
> right now the only way to construct the latest mmotm tree is through applying all
> the patches mentioned here at http://www.ozlabs.org/~akpm/mmotm/ on linux-next ?
linux-next should contain all of them already.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2019-01-07 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 23:28 akpm
2019-01-07 7:32 ` Anshuman Khandual
2019-01-07 8:43 ` Michal Hocko
2019-01-07 9:16 ` Anshuman Khandual
2019-01-07 9:23 ` Michal Hocko [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=20190107092356.GB31793@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--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=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