From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] [RESEND] Add cross compile to top level configuration file
Date: Tue, 16 Oct 2007 12:30:44 +0200 [thread overview]
Message-ID: <471492D4.6080009@qumranet.com> (raw)
In-Reply-To: <1192504130.5811.49.camel@thinkpad>
Jerone Young wrote:
> This new patch
btw, if it's an updated patch, don't put [RESEND] in there, it confuses
me. Put in v2, v3, etc. so I know it's something new.
A [RESEND] is for when I've dropped a patch without comment (which
should not happen normally).
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-16 10:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 19:12 [PATCH] Add cross compile to top level configuration file Jerone Young
2007-10-15 20:13 ` Anthony Liguori
[not found] ` <4713C9D5.3070001-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-15 20:35 ` Jerone Young
2007-10-15 20:51 ` Anthony Liguori
[not found] ` <4713D2BD.9040202-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-16 2:30 ` Jerone Young
2007-10-16 3:08 ` [PATCH] [RESEND] " Jerone Young
2007-10-16 9:59 ` Avi Kivity
[not found] ` <47148B90.2020607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 19:08 ` Jerone Young
2007-10-16 19:58 ` Avi Kivity
2007-10-16 10:30 ` Avi Kivity [this message]
2007-10-16 9:37 ` [PATCH] " Avi Kivity
2007-10-16 14:59 ` Anthony Liguori
[not found] ` <4714D1BA.6050504-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-16 19:51 ` Jerone Young
2007-10-16 20:03 ` Anthony Liguori
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=471492D4.6080009@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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.