From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:52772)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S9cUk-000460-Dj
	for qemu-devel@nongnu.org; Mon, 19 Mar 2012 09:19:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S9cUL-00033a-PY
	for qemu-devel@nongnu.org; Mon, 19 Mar 2012 09:19:29 -0400
Received: from mx1.redhat.com ([209.132.183.28]:23695)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S9cUL-00032z-Hh
	for qemu-devel@nongnu.org; Mon, 19 Mar 2012 09:19:05 -0400
Date: Mon, 19 Mar 2012 10:16:33 -0300
From: Luiz Capitulino <lcapitulino@redhat.com>
Message-ID: <20120319101633.25165f67@doriath.home>
In-Reply-To: <4F6699C1.6070905@cn.fujitsu.com>
References: <4F5FFC63.3060300@cn.fujitsu.com> <4F5FFE57.8010308@cn.fujitsu.com>
	<20120314141847.4557b4bb@doriath.home>
	<4F6699C1.6070905@cn.fujitsu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC][PATCH 11/14 v9] introduce a new monitor
 command 'dump' to dump guest's memory
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>, Dave Anderson <anderson@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, Eric Blake <eblake@redhat.com>

On Mon, 19 Mar 2012 10:28:17 +0800
Wen Congyang <wency@cn.fujitsu.com> wrote:

> > 'dump' is too generic, please call this dump-guest-memory-vmcore or something
> > more descriptive.
> 
> Hmm, dump-guest-memory-vmcore is too long. What about dump-guest-memory or
> dump-memory?

dump-guest-memory is acceptable, but we don't have problems with long names.
We prefer a long, but descriptive name, rather than a short & ambiguous one.