From: Michal Hocko <mhocko@suse.cz>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: mmotm 2012-06-21-16-20 uploaded
Date: Fri, 22 Jun 2012 11:23:27 +0200 [thread overview]
Message-ID: <20120622092327.GA5742@tiehlicka.suse.cz> (raw)
In-Reply-To: <20120621232149.F0286A026A@akpm.mtv.corp.google.com>
On Thu 21-06-12 16:21:49, Andrew Morton wrote:
> The mm-of-the-moment snapshot 2012-06-21-16-20 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
And from now on, memcg-devel tree[1] will not only pick up memcg
relevant patches but all patches in the mm section.
The tree was mainly focused on memcg development in the past but it
seems that having all mm and memcg patches together would be much easier
and also non memcg developers could benefit from it.
The tree will not be rebased (unlike linux-next) and after Linus
releases X.Y a new branch (since-X.Y) will be created and the current
stack rebased on top of vX.Y tag. Old branches stay at the place.
Please note that the tree doesn't substitute mmotm and all the changes
still fly through Andrew. The sole purpose of the tree is to make git
worklows for -mm development easier.
Thanks Andrew for helping me with this and tweaking his series file to
make it as much automated as possible.
---
[1] https://github.com/mstsxfx/memcg-devel.git
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-06-22 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 23:21 mmotm 2012-06-21-16-20 uploaded akpm
2012-06-21 23:34 ` Andrew Morton
2012-06-22 7:14 ` Minchan Kim
2012-06-22 8:14 ` viresh kumar
2012-06-22 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=20120622092327.GA5742@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.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 \
/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).