From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Paul Bolle <paul.bollee@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org,
Michal Hocko <mhocko@suse.cz>
Subject: Re: mmotm 2013-07-18-16-40 uploaded
Date: Fri, 19 Jul 2013 11:17:44 -0700 [thread overview]
Message-ID: <20130719111744.ce87390c8d8fa6b0b1c52eb6@linux-foundation.org> (raw)
In-Reply-To: <20130719180035.GI17812@cmpxchg.org>
On Fri, 19 Jul 2013 14:00:35 -0400 Johannes Weiner <hannes@cmpxchg.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.git
> > >by Michal Hocko. 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.
> > >
> > >
> > >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/?p=linux-mmotm.git;a=summary
> > >
> > >To develop on top of mmotm git:
> > >
> > > $ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> > > $ git remote update mmotm
> > > $ git checkout -b topic mmotm/master
> > > <make changes, commit>
> > > $ git send-email mmotm/master.. [...]
> > >
> > >To rebase a branch with older patches to a new mmotm release:
> > >
> > > $ git remote update mmotm
> > > $ git rebase --onto mmotm/master <topic base> topic
>
> Andrew, that workflow is actually meant for
> http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree
> (i.e. the git remote add mmotm <michal's tree> does not make much
> sense). Michal's tree is append-only, so all this precision-rebasing
> is unnecessary.
Gee, I haven't looked at that text in a while...
Could you guys please check it, propose any fixes we should make?
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 (3.x
or 3.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 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.git
by Michal Hocko. 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.
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/?p=linux-mmotm.git;a=summary
To develop on top of mmotm git:
$ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
$ git remote update mmotm
$ git checkout -b topic mmotm/master
<make changes, commit>
$ git send-email mmotm/master.. [...]
To rebase a branch with older patches to a new mmotm release:
$ git remote update mmotm
$ git rebase --onto mmotm/master <topic base> topic
The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
contains daily snapshots of the -mm tree. It is updated more frequently
than mmotm, and is untested.
A git copy of this tree is available at
http://git.cmpxchg.org/?p=linux-mmots.git;a=summary
and use of this tree is similar to
http://git.cmpxchg.org/?p=linux-mmotm.git, described above.
--
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:[~2013-07-19 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 23:41 akpm
2013-07-19 3:32 ` Paul Bolle
2013-07-19 18:00 ` Johannes Weiner
2013-07-19 18:17 ` Andrew Morton [this message]
2013-07-19 19:58 ` Johannes Weiner
2013-07-23 13:47 ` Michal Hocko
2013-07-23 13:44 ` Michal Hocko
2013-07-22 12:15 ` Paul Bolle
2013-07-22 15:37 ` Johannes Weiner
2013-07-22 12:42 ` Paul Bolle
2013-07-22 15:39 ` Johannes Weiner
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=20130719111744.ce87390c8d8fa6b0b1c52eb6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.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=paul.bollee@gmail.com \
/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