From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Anthony Liguori <anthony@codemonkey.ws>, KVM list <kvm@vger.kernel.org>
Subject: Re: Split kvm source tarballs
Date: Sun, 19 Apr 2009 11:26:08 +0300 [thread overview]
Message-ID: <49EAE020.30900@redhat.com> (raw)
In-Reply-To: <20090416201712.GA13500@infradead.org>
Christoph Hellwig wrote:
> Any idea when the split will happen?
>
I'm working on it, but hit a snag when rewriting upstream qemu commits
to match the official qemu.git:
- my repo and qemu.git used different -k options ("$keyword $"
squashing), so I can't match tree objects
- some non-UTF-8 characters got corrupted, so I can't match log messages
(some are dups anyway)
- I can't match the git-svn-id line since I ripped it off in
kvm-userspace.git
- I can't match the ordinal position of the commit in the changelog
since some bogus commits made their way into kvm-userspace.git
I expect I'll work around these issues, but it isn't like I have my
script ready to roll.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-04-19 8:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 14:21 Split kvm source tarballs Avi Kivity
2009-03-25 13:18 ` Anthony Liguori
2009-03-25 13:23 ` Avi Kivity
2009-03-25 13:44 ` Anthony Liguori
2009-03-25 16:47 ` Christoph Hellwig
2009-03-25 18:02 ` Avi Kivity
2009-03-25 18:17 ` Christoph Hellwig
2009-03-26 9:09 ` Avi Kivity
2009-03-26 22:48 ` Christoph Hellwig
2009-04-16 20:17 ` Christoph Hellwig
2009-04-18 22:13 ` Anthony Liguori
2009-04-19 8:26 ` Avi Kivity [this message]
2009-03-25 21:34 ` Anthony Liguori
2009-03-26 8:57 ` Christoph Hellwig
2009-03-26 18:19 ` Anthony Liguori
2009-03-26 22:48 ` Christoph Hellwig
2009-03-27 2:44 ` Anthony Liguori
2009-03-26 10:09 ` Avi Kivity
2009-03-26 18:19 ` 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=49EAE020.30900@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=hch@infradead.org \
--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).