From: Gerhard Wiesinger <lists@wiesinger.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Pulling regularly from QEMU git repository
Date: Sun, 9 May 2010 21:26:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1005092123540.12029@bbs.intern> (raw)
In-Reply-To: <4BD7F2EC.5020700@redhat.com>
On Wed, 28 Apr 2010, Avi Kivity wrote:
> 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.
Thnx for pulling more regularly.
BTW: Does it make sense to merge in one commit. I think with git it is
also possible to merge all upstream merge in original commits (n times vs.
1 time) which preserves history and patchsets better and cleaner.
Ciao,
Gerhard
--
http://www.wiesinger.com/
prev parent reply other threads:[~2010-05-09 19:27 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
2010-05-09 19:26 ` Gerhard Wiesinger [this message]
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=alpine.LFD.2.00.1005092123540.12029@bbs.intern \
--to=lists@wiesinger.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).