On 08/12/2013 12:54 PM, Gianluca Cecchi wrote:
> I just received a mail about what in subject ..
> Your membership in the mailing list Users has been disabled due to
> excessive bounces....
> I re-enabled my membership in the mean time.
> Just to know if it is actually a problem of mine (aka gmail and no
> configuration change at all) or list related.
> Users mailing list
moving to infra mailing list
Adding the infra team.
Can you please take a look?
----- Original Message -----
> From: "Shubhendu Tripathi" <shtripat(a)redhat.com>
> To: "engine-devel" <engine-devel(a)ovirt.org>
> Sent: Monday, May 27, 2013 10:09:58 AM
> Subject: [Engine-devel] Regarding access to ovirt.org for creating feature pages
> Hi All,
> I have joined RedHat this month and work with RHSC team.
> I need to create a feature page on Ovirt WIKI, and so raised a request
> for the same to get an id created.
> I have not received any confirmation till now.
> Kindly let me know if something is missing or I need to follow some
> other process.
> ID Created: shtripat
> Email Id: shtripat(a)redhat.com
> Thanks and Regards,
> Shubhendu Tripathi
> Engine-devel mailing list
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
Content-Type: text/plain; charset=UTF-8
I think that I accidentally dropped the request on mailman admin page.
So I'll resend it on he's behalf.
We should have some spam filtering :S
-------- Original Message --------
Subject: running network functional tests
Date: Mon, 12 Aug 2013 04:58:04 -0400 (EDT)
From: Giuseppe Vallarelli <gvallare(a)redhat.com>
To: infra <infra(a)ovirt.org>
CC: David Caro Estevez <dcaroest(a)redhat.com>
Just recently we added networking functional tests and we would like
to have them running when we submit patches network related, i.e.
going to affect network modules. Displaying success or failure
as it happens with the current unittests.
- OS Fedora 19/RHEL6.4 should not matter.
- Kernel module used: bonding, dummy.
- No more than one 'instance' of networkTests should run
on a specific host, simply because we use some global
constants to identify network name vlan id and so on.
- Ideally we can use a previously proposed idea of commit tag
where for example @networking is provided in the commit msg
title to identify the need of running also the network
- We should be able to run at the same time functional networking
tests and unit tests - I don't expect any conflicts.
Would be cool to have a test run before -1s all networking patches
in case of problems :-)
Let me know if more information are needed.
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
-----END PGP SIGNATURE-----