From: Sedat Dilek <sedat.dilek@googlemail.com>
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
Subject: Re: mmotm 2010-12-23-16-58 uploaded
Date: Fri, 24 Dec 2010 13:15:26 +0100 [thread overview]
Message-ID: <AANLkTinegsqmSzXqqrF930abQfOBu6_MH1EToupKV214@mail.gmail.com> (raw)
In-Reply-To: <201012240132.oBO1W8Ub022207@imap1.linux-foundation.org>
On Fri, Dec 24, 2010 at 1:58 AM, <akpm@linux-foundation.org> wrote:
> The mm-of-the-moment snapshot 2010-12-23-16-58 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
>
> and will soon be available at
>
> git://zen-kernel.org/kernel/mmotm.git
>
The readme in [1] lists a wrong browseable GIT-repo URL:
"Alternatively, these patches are available in a git repository at
git: git://zen-kernel.org/kernel/mmotm.git
gitweb: http://git.zen-kernel.org/?p=kernel/mmotm.git;a=summary"
Correct would be [2]:
gitweb: http://git.zen-kernel.org/mmotm/
> It contains the following patches against 2.6.37-rc7:
>
[...]
> linux-next-git-rejects.patch
Hm, the content of this patch looks a bit strange.
Is that a post-cleanup patch to linux-next merge?
- Sedat -
[1] http://userweb.kernel.org/~akpm/mmotm/mmotm-readme.txt
[2] http://git.zen-kernel.org/mmotm/
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-12-24 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 0:58 akpm
2010-12-24 12:15 ` Sedat Dilek [this message]
2010-12-24 13:04 ` Andrew Morton
2010-12-24 17:52 ` [PATCH -mmotm] kptr_restrict: fix build when PRINTK not enabled Randy Dunlap
2010-12-27 2:13 ` mmotm 2010-12-23-16-58 uploaded Randy Dunlap
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=AANLkTinegsqmSzXqqrF930abQfOBu6_MH1EToupKV214@mail.gmail.com \
--to=sedat.dilek@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=sedat.dilek@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