public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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 1/2] [RESEND] Enable user directory	configure script for	cross compile
Date: Tue, 09 Oct 2007 18:02:26 +0200	[thread overview]
Message-ID: <470BA612.5010700@qumranet.com> (raw)
In-Reply-To: <1191945649.5802.2.camel@laptop>

Jerone Young wrote:
> I believe the problem is that I am not generating my patches in git
> format. I have been using a mercuial mq tree to generate the patches I
> have been sending. While they apply fine with patch command, apparently
> git needs the patches fomatted correctly.
>
>   

git generally knows how to apply things... perhaps your mq tree is stale 
and you're generating patches against an older snapshot?


-- 
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/

  reply	other threads:[~2007-10-09 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09  5:19 [PATCH 1/2] [RESEND] Enable user directory configure script for cross compile Jerone Young
2007-10-09 13:26 ` Avi Kivity
     [not found]   ` <470B8175.6060806-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-09 16:00     ` Jerone Young
2007-10-09 16:02       ` Avi Kivity [this message]
     [not found]         ` <470BA612.5010700-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-09 16:44           ` Jerone Young

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=470BA612.5010700@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox