From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Baruch Even <baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Duplicate content in files
Date: Tue, 19 Jun 2007 16:11:04 -0500 [thread overview]
Message-ID: <46784668.2060106@codemonkey.ws> (raw)
In-Reply-To: <46784183.4070502-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
Baruch Even wrote:
> Luca wrote:
>
>> On 6/19/07, Baruch Even <baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org> wrote:
>>
>>> Hello,
>>>
>>> I've tried to diff kvm-28 qemu directory with qemu 0.9.0 and I see that
>>> some files in the kvm sources have the content of the file duplicated,
>>> f.ex. qemu/hw/mips_int.c has it's own content twice in the kvm tree, it
>>> only has it once in qemu as it should be. Look for the include
>>> directives and you'll see what I mean.
>>>
>>> There are several other files like that.
>>>
>> Funny :-) Clearly they're unused in KVM (only x86* is compiled)
>> otherwise the linker would scream :P
>> According to GIT those files haven't been touched, something went
>> wrong during the initial import.
>>
>
> My problem is that I'm now looking at applying "the kvm patch" into the
> Debian qemu so we will remove the need for a special package, in this
> case these files will become in use and I'd like to be able to easily
> track kvm upstream and update the Debian qemu package.
>
> For this to happen I need the kvm tree to be clean in relation to qemu
> and this issue is going to make it a pain to maintain such a patch.
>
A patch to eliminate this stuff would be very nice!
Regards,
Anthony Liguori
> Will the kvm dev folks accept a patch to correct such mistakes?
> Baruch
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-19 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 20:34 Duplicate content in files Baruch Even
[not found] ` <46783DC8.2010006-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
2007-06-19 20:46 ` Luca
[not found] ` <68676e00706191346r615b798emd90be772ac3bdd45-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-19 20:50 ` Baruch Even
[not found] ` <46784183.4070502-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
2007-06-19 21:11 ` Anthony Liguori [this message]
[not found] ` <46784668.2060106-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-06-19 21:36 ` Baruch Even
[not found] ` <46784C46.206-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
2007-06-20 7:51 ` Avi Kivity
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=46784668.2060106@codemonkey.ws \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=baruch-6P1Dz+XQpLLYtjvyW6yDsg@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.