From: Dave Young <dyoung@redhat.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH] move vm tools from Documentation/vm/ to tools/
Date: Wed, 01 Feb 2012 17:53:44 +0800 [thread overview]
Message-ID: <4F290BA8.9030606@redhat.com> (raw)
In-Reply-To: <CAOJsxLEnn-5X5q=1p07twxm5EuyQo7cOBBfFQXUeMGi3Pvd46w@mail.gmail.com>
On 02/01/2012 04:44 PM, Pekka Enberg wrote:
> On Wed, Feb 1, 2012 at 10:30 AM, Wu Fengguang <fengguang.wu@intel.com> wrote:
>> Will git-mv end up with a better commit?
>
> Just use
>
> git format-patch -C
good idea, patch looks clean with -C. So there should be no much problem
for review. Also because there's also Makefile changes, I want to still
send as one patch with all changes. How do you think?
>
> to generate the patch and it should be fine.
>
>>> BTW, I think tools/slub/slabinfo.c should be included in tools/vm/ as
>>> well, will move it in v2 patch
>>
>> CC Christoph. Maybe not a big deal since it's already under tools/.
>
> I'm certainly fine with moving it to tools/vm.
--
Thanks
Dave
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Young <dyoung@redhat.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH] move vm tools from Documentation/vm/ to tools/
Date: Wed, 01 Feb 2012 17:53:44 +0800 [thread overview]
Message-ID: <4F290BA8.9030606@redhat.com> (raw)
In-Reply-To: <CAOJsxLEnn-5X5q=1p07twxm5EuyQo7cOBBfFQXUeMGi3Pvd46w@mail.gmail.com>
On 02/01/2012 04:44 PM, Pekka Enberg wrote:
> On Wed, Feb 1, 2012 at 10:30 AM, Wu Fengguang <fengguang.wu@intel.com> wrote:
>> Will git-mv end up with a better commit?
>
> Just use
>
> git format-patch -C
good idea, patch looks clean with -C. So there should be no much problem
for review. Also because there's also Makefile changes, I want to still
send as one patch with all changes. How do you think?
>
> to generate the patch and it should be fine.
>
>>> BTW, I think tools/slub/slabinfo.c should be included in tools/vm/ as
>>> well, will move it in v2 patch
>>
>> CC Christoph. Maybe not a big deal since it's already under tools/.
>
> I'm certainly fine with moving it to tools/vm.
--
Thanks
Dave
next prev parent reply other threads:[~2012-02-01 9:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 6:34 [PATCH] move vm tools from Documentation/vm/ to tools/ Dave Young
2012-02-01 6:45 ` Cong Wang
2012-02-01 7:39 ` Dave Young
2012-02-01 7:32 ` Pekka Enberg
2012-02-01 7:32 ` Pekka Enberg
2012-02-01 7:41 ` Dave Young
2012-02-01 7:41 ` Dave Young
2012-02-01 8:30 ` Wu Fengguang
2012-02-01 8:30 ` Wu Fengguang
2012-02-01 8:44 ` Pekka Enberg
2012-02-01 8:44 ` Pekka Enberg
2012-02-01 9:53 ` Dave Young [this message]
2012-02-01 9:53 ` Dave Young
2012-02-01 9:53 ` Dave Young
2012-02-01 9:53 ` Dave Young
2012-02-01 14:40 ` Christoph Lameter
2012-02-01 14:40 ` Christoph Lameter
2012-02-01 21:17 ` Andrew Morton
2012-02-02 2:13 ` Dave Young
2012-02-02 7:32 ` Cong Wang
2012-02-02 19:58 ` Andrew Morton
2012-02-02 19:56 ` Andrew Morton
2012-02-03 1:31 ` Dave Young
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=4F290BA8.9030606@redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.