[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpVA--TR39AnrjQ6j14W7wYOLr62B52uVj5_RGAUMex8Sg@mail.gmail.com>
Date: Thu, 25 Aug 2011 11:44:53 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: Alexander Graf <agraf@...e.de>
Cc: Pekka Enberg <penberg@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, Avi Kivity <avi@...hat.com>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
"kvm@...r.kernel.org list" <kvm@...r.kernel.org>,
qemu-devel Developers <qemu-devel@...gnu.org>
Subject: Re: [PATCH] KVM: Add wrapper script around Qemu to test kernels
On Thu, Aug 25, 2011 at 4:35 AM, Alexander Graf <agraf@...e.de> wrote:
>
> On 24.08.2011, at 00:31, Américo Wang wrote:
>
>> On Wed, Aug 24, 2011 at 1:19 PM, Pekka Enberg <penberg@...nel.org> wrote:
>>>
>>> It's nice to see such an honest attempt at improving QEMU usability, Alexander!
>>>
>>> One comment: in my experience, having shell scripts under
>>> Documentation reduces the likelihood that people actually discover
>>> them so you might want to consider putting it under scripts or tools.
>>>
>>
>> I was going to give the same suggestion, +1 for tools/ directory.
>
> Well, scripts/ is a flat directory where I can just throw in the script. Tools however is split by tool and creating a full new directory for only a single script sounds a bit like overkill to me. I'll move it to scripts/ for now :)
How about the directory tools/testing/ ?
scripts/ is mainly for the tools/utilities we use to build kernel or
do kernel dev,
it is not so suitable for your script IMHO.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists