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, Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: mmotm 2012-09-06-16-46 uploaded
Date: Fri, 7 Sep 2012 17:12:47 +0200 [thread overview]
Message-ID: <20120907151246.GB3688@dhcp22.suse.cz> (raw)
In-Reply-To: <20120906234735.1B54B20004E@hpza10.eem.corp.google.com>
[CCing Wu Fengguang so that he can update the link to the new tree
location]
On Thu 06-09-12 16:47:34, Andrew Morton wrote:
[...]
> A git tree which contains the memory management portion of this tree is
> maintained at https://github.com/mstsxfx/memcg-devel.git by Michal Hocko.
I have finally added the tree to the kernel.org infrastructure
(http://git.kernel.org/?p=linux/kernel/git/mhocko/mm.git;a=summary).
Both (k.org and github) have the same branches and layout and I will be
updating both until the end of this month. Github will be discontinued
since 1st Oct.
The switch is really easy. Just add a new remote
$ git remote add mm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
and move your local tracking branches to point to the new remote.
> It contains the patches which are between the "#NEXT_PATCHES_START mm" and
> "#NEXT_PATCHES_END" markers, from the series file,
> http://www.ozlabs.org/~akpm/mmotm/series.
--
Michal Hocko
SUSE Labs
--
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>
next prev parent reply other threads:[~2012-09-07 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 23:47 mmotm 2012-09-06-16-46 uploaded akpm
2012-09-07 15:12 ` Michal Hocko [this message]
2012-09-07 15:22 ` Fengguang Wu
2012-09-07 15:23 ` Michal Hocko
2012-09-07 23:45 ` mmotm 2012-09-06-16-46 uploaded (fs/binfmt_aout) Randy Dunlap
2012-09-11 22:17 ` Andrew Morton
2012-09-08 0:39 ` mmotm 2012-09-06-16-46 uploaded (drivers/video/backlight/lm3639_bl) Randy Dunlap
2012-09-10 0:11 ` gshark
2012-09-08 0:50 ` mmotm 2012-09-06-16-46 uploaded (drivers/misc/lis3lv02d/lis3lv02d_spi.c) Randy Dunlap
2012-09-08 10:44 ` Daniel Mack
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=20120907151246.GB3688@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--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).