On 07/26/2012 10:11 PM, Lucas Meneghel Rodrigues wrote:
On Thu, 2012-07-26 at 14:50 -0400, Don Zickus wrote:
On Thu, Jul 26, 2012 at 03:03:27PM -0300, Lucas Meneghel Rodrigues wrote:
This is a respin of the scheduler email format work, mostly
to verify whether the new patchwork instance (and the mailing list)
is working fine.

Just a follow question about the mailing list.  Is this just an internal
Red Hat mailing list for the internal version of autotest you are
maintaining?

Nope, long story short, I want to shutdown the test.kernel.org box for
good, therefore I have to move the mailing list. this is the new
upstream list, a public one.

What's its role that the current none kernel autotest do not provide?


Trying to figure out if these are patches that would go upstream
(external) or not?

These are external, public patches to the new upstream mailing list.

Please check the latest messages on the (soon to be shutdown)
[email protected] mailing list.

Cheers,
Don


Lucas Meneghel Rodrigues (4):
   scheduler.scheduler_models: Tidy up results format email
   shared.git: Remove double quotes on result of get_topmost_commit
   virt.installer: Register keyval with installed sw versions
   scheduler_models: Allow to specify list of keyvals on sched emails

  client/shared/git.py          |    2 +-
  client/virt/base_installer.py |   17 ++++++
  client/virt/tests/build.py    |    1 +
  global_config.ini             |    2 +
  scheduler/scheduler_models.py |  125 ++++++++++++++++++++++++++++++++---------
  5 files changed, 119 insertions(+), 28 deletions(-)

--
1.7.10.4

_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel


_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel


_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel

Reply via email to