From: Avi Kivity <avi@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: kvm@vger.kernel.org
Subject: Re: Pulling regularly from QEMU git repository
Date: Wed, 28 Apr 2010 11:33:48 +0300 [thread overview]
Message-ID: <4BD7F2EC.5020700@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004280632020.22120@bbs.intern>
On 04/28/2010 07:37 AM, Gerhard Wiesinger wrote:
> Hello,
>
> I saw that KVM git repository is not updated from QEMU repository very
> often. Is it possible to integrate QEMU git tree into KVM git
> regularly as qemu git tree is very dynamic. E.g. last commit was more
> than 2 weeks ago. I think it is necessary to integrate early and often
> as a lot of bugs are fixed.
>
We usually pull at least once a week, but sometimes we are lazy.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-04-28 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 4:37 Pulling regularly from QEMU git repository Gerhard Wiesinger
2010-04-28 8:33 ` Avi Kivity [this message]
2010-05-09 19:26 ` Gerhard Wiesinger
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=4BD7F2EC.5020700@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lists@wiesinger.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;
as well as URLs for NNTP newsgroup(s).