All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Reitan <mailinglists@unix-scripts.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] for xend init script and xend python script
Date: Fri, 29 Oct 2010 10:57:22 -0700	[thread overview]
Message-ID: <4CCB0B02.80706@unix-scripts.com> (raw)
In-Reply-To: <19656.20481.596734.306544@mariner.uk.xensource.com>

On 10/27/2010 9:14 AM, Ian Jackson wrote:
> ShaunR writes ("[Xen-devel] Re: [PATCH] for xend init script and xend python script"):
>> I see in the new xencommons that there's a XENCONSOLED_ARGS env which
>> could hold all this info and be set in /etc/sysconfig/xencommons but I'm
>> worried about it being overwritten by some of the checks in the script.
>
> Oh, yes.  It would be better if the xencommons script prepended to the
> ARGS (so that settings in the /etc/default file can override) rather
> than unconditionally setting, or if we had two variables.
>
>> Either way works i guess, i like separate options because i think it's
>> easier for people to write automated scripts against to ensure the
>> options they want are enabled.
>
> Yes.  I'd be happy to take a patch to implement separate options in
> xencommons in unstable.
>
> Ian.

Ian,

I'll go ahead and implement this and submit a patch, i'm alittle busy 
this week.  How long do you think i have until unstable is merged?  I 
would like to make sure this this patch included into the next version 
so trying to figure out my time line :)

--
Shaun Retian
Chief Technical Officer
Network Data Center Host, Inc.
http://www.NDCHost.com

  reply	other threads:[~2010-10-29 17:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 19:47 [PATCH] for xend init script and xend python script ShaunR
2010-10-26 16:21 ` Ian Jackson
2010-10-26 17:38   ` ShaunR
2010-10-27 16:14     ` Ian Jackson
2010-10-29 17:57       ` Shaun Reitan [this message]
2010-10-29 18:02         ` Ian Jackson
2010-10-29 18:03           ` Ian Jackson

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=4CCB0B02.80706@unix-scripts.com \
    --to=mailinglists@unix-scripts.com \
    --cc=xen-devel@lists.xensource.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 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.