From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, npiggin@kernel.dk, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, kosaki.motohiro@jp.fujitsu.com,
cl@linux.com, kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH 0/3] Unmapped page cache control (v5)
Date: Fri, 1 Apr 2011 23:01:45 +0530 [thread overview]
Message-ID: <20110401173145.GT2879@balbir.in.ibm.com> (raw)
In-Reply-To: <20110330223231.e1f149eb.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> [2011-03-30 22:32:31]:
> On Thu, 31 Mar 2011 10:57:03 +0530 Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
> > * Andrew Morton <akpm@linux-foundation.org> [2011-03-30 16:36:07]:
> >
> > > On Wed, 30 Mar 2011 11:00:26 +0530
> > > Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > >
> > > > Data from the previous patchsets can be found at
> > > > https://lkml.org/lkml/2010/11/30/79
> > >
> > > It would be nice if the data for the current patchset was present in
> > > the current patchset's changelog!
> > >
> >
> > Sure, since there were no major changes, I put in a URL. The main
> > change was the documentation update.
>
> Well some poor schmuck has to copy and paste the data into the
> changelog so it's still there in five years time. It's better to carry
> this info around in the patch's own metedata, and to maintain
> and update it.
>
Agreed, will do.
--
Three Cheers,
Balbir
--
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 internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-04-01 17:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 5:30 [PATCH 0/3] Unmapped page cache control (v5) Balbir Singh
2011-03-30 5:31 ` [PATCH 1/3] Move zone_reclaim() outside of CONFIG_NUMA (v5) Balbir Singh
2011-03-30 5:31 ` [PATCH 2/3] Refactor zone_reclaim code (v5) Balbir Singh
2011-03-30 5:32 ` [PATCH 3/3] Provide control over unmapped pages (v5) Balbir Singh
2011-03-30 23:35 ` Andrew Morton
2011-03-31 5:52 ` Balbir Singh
2011-03-30 23:36 ` [PATCH 0/3] Unmapped page cache control (v5) Andrew Morton
2011-03-31 5:27 ` Balbir Singh
2011-03-31 5:32 ` Andrew Morton
2011-04-01 17:31 ` Balbir Singh [this message]
2011-03-31 5:40 ` KOSAKI Motohiro
2011-03-31 8:28 ` Balbir Singh
2011-04-01 7:56 ` KOSAKI Motohiro
2011-04-01 13:12 ` Balbir Singh
2011-04-01 13:21 ` KOSAKI Motohiro
2011-04-01 18:04 ` Balbir Singh
2011-04-03 9:39 ` KOSAKI Motohiro
2011-03-31 20:13 ` Christoph Lameter
2011-04-01 13:17 ` KOSAKI Motohiro
2011-04-01 14:50 ` Christoph Lameter
2011-04-03 9:44 ` KOSAKI Motohiro
2011-04-03 18:45 ` Christoph Lameter
2011-04-01 23:10 ` Satoru Moriya
2011-04-02 1:10 ` Dave Chinner
2011-04-03 9:32 ` KOSAKI Motohiro
2011-04-04 0:19 ` Dave Chinner
2011-04-04 12:05 ` KOSAKI Motohiro
2011-04-03 18:41 ` Christoph Lameter
2011-03-31 21:40 ` Dave Chinner
2011-04-01 3:08 ` Balbir Singh
2011-04-01 5:31 ` Dave Chinner
2011-04-01 3:18 ` KOSAKI Motohiro
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=20110401173145.GT2879@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@kernel.dk \
/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).