All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Veillard <veillard@redhat.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	libvir-list@redhat.com, Ian Jackson <ian.jackson@citrix.com>,
	berrange@redhat.com,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: libvirt / libxl testing emails
Date: Fri, 6 Jun 2014 17:32:30 +0800	[thread overview]
Message-ID: <20140606093230.GB28693@redhat.com> (raw)
In-Reply-To: <1402043146.29759.11.camel@kazak.uk.xensource.com>

On Fri, Jun 06, 2014 at 09:25:46AM +0100, Ian Campbell wrote:
> On Wed, 2014-06-04 at 00:00 +0800, Daniel Veillard wrote:
> > On Tue, Jun 03, 2014 at 03:16:49PM +0100, George Dunlap wrote:
> > > Ian / Ian,
> > > 
> > > Daniel V. was lurking on a recent CentOS Virt SIG IRC meetings, and asked
> > > about testing the libvirt git repo against libxl.  I mentioned that we
> > > already had some basic tests to do that, and he asked whether it would make
> > > sense to have the push gate e-mail the libvirt list.
> > > 
> > > I have no idea how the libvirt people feel about that, so I'll let DV make
> > > his case, and also let he Ians give their opinions.
> > 
> >   Actually Dan Berrange should be included. I think the nicest would
> > be a private ping and the information available online,
> 
> Why private and not to the libvir list?

  Well the point is that the libvir-list is already high traffic
and avoiding automated mails to it would help. Also the compile
box doesn't send mail directly to the list in case of breakage either,
so that would be coherent.

> The information is available online via the test report (which don't
> stay around forever, but for weeks at least).
> 
> I'm happy to do whatever you guys would prefer, just let me know.

  Do you have a pointer to where the test reports sit, that would be
helpful as a first step :-)

    thanks,

Daniel
-- 
Daniel Veillard      | Open Source and Standards, Red Hat
veillard@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

  parent reply	other threads:[~2014-06-06  9:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 14:16 libvirt / libxl testing emails George Dunlap
2014-06-03 14:30 ` [libvirt] " Daniel P. Berrange
2014-06-03 14:37   ` George Dunlap
     [not found]   ` <538DDDA4.20302@eu.citrix.com>
2014-06-03 14:45     ` Ian Campbell
2014-06-03 16:00 ` Daniel Veillard
     [not found] ` <20140603160041.GC14854@redhat.com>
2014-06-06  8:25   ` Ian Campbell
     [not found]   ` <1402043146.29759.11.camel@kazak.uk.xensource.com>
2014-06-06  9:32     ` Daniel Veillard [this message]
2014-06-06  9:47       ` Ian Campbell

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=20140606093230.GB28693@redhat.com \
    --to=veillard@redhat.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=berrange@redhat.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=libvir-list@redhat.com \
    --cc=xen-devel@lists.xen.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.