[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <451ec03f-d669-fcd0-11c7-f7fef9f85a56@arm.com>
Date: Mon, 7 Jan 2019 14:46:43 +0530
From: Anshuman Khandual <anshuman.khandual@....com>
To: Michal Hocko <mhocko@...nel.org>
Cc: akpm@...ux-foundation.org, broonie@...nel.org,
sfr@...b.auug.org.au, linux-next@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, mm-commits@...r.kernel.org
Subject: Re: mmotm 2018-12-21-15-28 uploaded
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@...ux-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 ?
Powered by blists - more mailing lists