From: Anthony Liguori <aliguori@us.ibm.com>
To: Itamar Reis Peixoto <itamar@ispbrasil.com.br>
Cc: xen-devel@lists.xensource.com
Subject: Re: Patch to xm create search domU config in /etc/xen/auto
Date: Mon, 03 Apr 2006 11:39:11 -0500 [thread overview]
Message-ID: <44314FAF.3090709@us.ibm.com> (raw)
In-Reply-To: <001901c65733$e270a6e0$0100000a@lualele>
Hope this doesn't appear to be singling you out, but this is a good
opportunity to highlight some patch submitting good practices:
1) Your patch doesn't contain a Signed-off-by line so it cannot be applied.
2) Your patch is attached with an improper MIME type. If you cannot use
a more sane mailer, you should also inline your patches (it's impossible
for me to actually comment on your patch in a note without some nasty
copy-paste stuff).
3) You include no explanation of why your patch is needed. It seems
somewhat arbitrary to add /etc/xen/auto to the default search path. Why
do you need this and why do you think other people would need this?
4) Your patch is based at a weird location (within tools/). It's
usually best to patch at the top of the repository (diff -u
a/tools/xen/xm/create.py b/tools/....). Actually, if you just use hg
export, it'll do the right thing for you.
Please resubmit with the appropriate corrections.
Thanks!
Regards,
Anthony Liguori
Itamar Reis Peixoto wrote:
> attached.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2006-04-03 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 15:32 Patch to xm create search domU config in /etc/xen/auto Itamar Reis Peixoto
2006-04-03 16:39 ` Anthony Liguori [this message]
2006-04-03 17:50 ` Itamar Reis Peixoto
2006-04-03 17:56 ` Anthony Liguori
2006-04-04 14:06 ` Molle Bestefich
2006-04-05 15:31 ` Mark Williamson
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=44314FAF.3090709@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=itamar@ispbrasil.com.br \
--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.