From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Steve Howard <showard@google.com>
Cc: John Admanski <jadmanski@google.com>,
autotest@test.kernel.org, kvm@vger.kernel.org,
Scott Zawalski <scottz@google.com>
Subject: Re: [Autotest] [PATCH] Move global configuration files to client dir
Date: Wed, 11 Nov 2009 22:09:59 -0200 [thread overview]
Message-ID: <1257984599.2789.1.camel@localhost.localdomain> (raw)
In-Reply-To: <5029f4960911111559l504ef53dh3242ed58e54c7c2a@mail.gmail.com>
On Wed, 2009-11-11 at 15:59 -0800, Steve Howard wrote:
> On Wed, Nov 11, 2009 at 9:30 AM, John Admanski <jadmanski@google.com> wrote:
> > I thought about it a bit more:
> >
> > Maybe a better approach would be to have the global_config module find
> > the ini file in job.autodir (so on a client it would show up in the
> > client/ dir, and on the server in the "true" top-level dir) and then
> > add support to Autotest.run so that it copies over the server's copy
> > of the config to the client before launching a client job?
> >
> > So that way it would "just work", and changes to the server config
> > would automatically get pushed out to client jobs. All without moving
> > the file that users running a server need to edit. And it's not too
> > complex of a design; the Autotest.run code already needs to copy over
> > a few files by hand like control files so copying over the config too
> > isn't too much of a burden.
>
> For the record, I agree with John's proposed approach.
Yes, I am preparing a patch using John's idea, will send it tomorrow
morning.
Thanks guys,
> Steve
prev parent reply other threads:[~2009-11-12 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 11:24 [PATCH] Move global configuration files to client dir Lucas Meneghel Rodrigues
2009-11-11 15:32 ` [Autotest] " John Admanski
2009-11-11 17:16 ` Lucas Meneghel Rodrigues
2009-11-11 17:30 ` John Admanski
2009-11-11 17:35 ` Martin Bligh
2009-11-11 17:37 ` John Admanski
2009-11-11 17:45 ` Scott Zawalski
2009-11-11 23:41 ` John Admanski
2009-11-11 23:59 ` Steve Howard
2009-11-12 0:09 ` Lucas Meneghel Rodrigues [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=1257984599.2789.1.camel@localhost.localdomain \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=jadmanski@google.com \
--cc=kvm@vger.kernel.org \
--cc=scottz@google.com \
--cc=showard@google.com \
/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