From: Wing D Lizard <wingedlizard@nc.rr.com>
To: qemu-devel@nongnu.org, gleb@qumranet.com
Subject: [Qemu-devel] many messages per hour from Gleb Natapov
Date: Thu, 30 Oct 2008 09:14:55 -0400 [thread overview]
Message-ID: <4909B34F.6020800@nc.rr.com> (raw)
In-Reply-To: <20080616130135.24174.93474.stgit@gleb-debian.qumranet.com.qumra net.com>
is anybody else getting these? How can I stop - I get about 200 per day.
awl
Gleb Natapov wrote:
> There was no additional comments last time I sent this patch series and
> it was not yet committed to the SVN. Resend it for review/inclusion.
>
> This is updated version of the patch series. The patch #5 checks libuuid
> availability and uses it for UUID generation if present, but it is
> optional so if people think that libvirt is a better place for UUID generation
> just don't apply the last patch.
>
> --
> Gleb.
>
>
>
>From - Thu Oct 30 09:07:56 2008
X-Account-Key: account5
X-UIDL:
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:
Return-Path: <qemu-devel-bounces+wingedlizard=nc.rr.com@nongnu.org>
Received: from cdptpa-mxlb.mail.rr.com ([10.127.255.7])
by cdptpa-imta06.mail.rr.com with ESMTP
id <20080616132101.HDDT17935.cdptpa-imta06.mail.rr.com@cdptpa-mxlb.mail.rr.com>
for <wingedlizard@nc.rr.com>; Mon, 16 Jun 2008 13:21:01 +0000
X-IronPort: cdptpa-mx04.mail.rr.com 625824684
X-RR-Connecting-IP: 199.232.76.165
Received: from lists.gnu.org ([199.232.76.165])
by cdptpa-mxlb.mail.rr.com with ESMTP; 16 Jun 2008 13:21:00 +0000
Received: from localhost ([127.0.0.1]:58953 helo=lists.gnu.org)
by lists.gnu.org with esmtp (Exim 4.43)
id 1K8Edn-0001Ch-1i
for wingedlizard@nc.rr.com; Mon, 16 Jun 2008 09:20:59 -0400
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
id 1K8EdX-0001CY-1H
for qemu-devel@nongnu.org; Mon, 16 Jun 2008 09:20:43 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
id 1K8EdV-0001CI-HY
for qemu-devel@nongnu.org; Mon, 16 Jun 2008 09:20:42 -0400
Received: from [199.232.76.173] (port=53568 helo=monty-python.gnu.org)
by lists.gnu.org with esmtp (Exim 4.43) id 1K8EdV-0001CF-CF
for qemu-devel@nongnu.org; Mon, 16 Jun 2008 09:20:41 -0400
Received: from il.qumranet.com ([212.179.150.194]:18170)
by monty-python.gnu.org with esmtp (Exim 4.60)
(envelope-from <gleb@qumranet.com>) id 1K8EdU-0004dT-Nf
for qemu-devel@nongnu.org; Mon, 16 Jun 2008 09:20:41 -0400
Received: from gleb-debian.qumranet.com (unknown [172.16.15.143])
by il.qumranet.com (Postfix) with ESMTP id CDBFE250310
for <qemu-devel@nongnu.org>; Mon, 16 Jun 2008 16:20:36 +0300 (IDT)
Received: by gleb-debian.qumranet.com (Postfix, from userid 587)
id E1A2718D563; Mon, 16 Jun 2008 16:20:36 +0300 (IDT)
Date: Mon, 16 Jun 2008 16:20:36 +0300
From: Gleb Natapov <gleb@qumranet.com>
To: qemu-devel@nongnu.org
Message-ID: <20080616130135.24174.93474.stgit@gleb-debian.qumranet.com.qumra
net.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 1)
Subject: [Qemu-devel] [RESEND PATCH v3 0/5] Add UUID support.
X-BeenThere: qemu-devel@nongnu.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Sender: qemu-devel-bounces+wingedlizard=nc.rr.com@nongnu.org
Errors-To: qemu-devel-bounces+wingedlizard=nc.rr.com@nongnu.org
There was no additional comments last time I sent this patch series and
it was not yet committed to the SVN. Resend it for review/inclusion.
This is updated version of the patch series. The patch #5 checks libuuid
availability and uses it for UUID generation if present, but it is
optional so if people think that libvirt is a better place for UUID generation
just don't apply the last patch.
--
Gleb.
prev parent reply other threads:[~2008-10-30 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080616130135.24174.93474.stgit@gleb-debian.qumranet.com.qumranet.com>
2008-06-16 13:01 ` [Qemu-devel] [RESEND PATCH v3 1/5] Add OUT support to vmport Gleb Natapov
2008-06-16 13:01 ` [Qemu-devel] [RESEND PATCH v3 2/5] Add -uuid command line option Gleb Natapov
2008-06-16 13:01 ` [Qemu-devel] [RESEND PATCH v3 3/5] Add "info uuid" command to monitor Gleb Natapov
2008-06-16 13:01 ` [Qemu-devel] [RESEND PATCH v3 4/5] Add support for UUID query to vmport interface Gleb Natapov
2008-06-16 13:02 ` [Qemu-devel] [RESEND PATCH v3 5/5] Use libuuid if available Gleb Natapov
2008-06-17 22:04 ` [Qemu-devel] [RESEND PATCH v3 0/5] Add UUID support Fabrice Bellard
2008-06-18 6:07 ` Gleb Natapov
2008-06-18 12:13 ` Jamie Lokier
2008-06-23 8:52 ` Gleb Natapov
2008-10-15 12:46 ` Wing D Lizard
2008-10-30 13:14 ` Wing D Lizard [this message]
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=4909B34F.6020800@nc.rr.com \
--to=wingedlizard@nc.rr.com \
--cc=gleb@qumranet.com \
--cc=qemu-devel@nongnu.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 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).