qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PC Bios source code?
Date: Thu, 08 Nov 2007 16:58:45 +0200	[thread overview]
Message-ID: <47332425.70109@qumranet.com> (raw)
In-Reply-To: <fb249edb0711080641m1f6ce984s98c15bb3bca00a35@mail.gmail.com>

andrzej zaborowski wrote:
>>>
>>> As you said yourself, there's also a .diff file. It should contain all
>>> differences between original source code and modified source code. You
>>> can apply it to the original source code with patch.
>>>
>>>       
>> But how can he tell what the original source is?
>>
>> At the minimum the version numbers of all source files in the bochs cvs
>> need to be listed.
>>     
>
> The .diff contains revision numbers for all files.
>
>   

Only for files that are changed by said .diff.

-- 
error compiling committee.c: too many arguments to function

      reply	other threads:[~2007-11-08 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  1:34 [Qemu-devel] PC Bios source code? Jun Koi
2007-11-08 14:00 ` Andreas Färber
2007-11-08 14:26   ` Avi Kivity
2007-11-08 14:41     ` andrzej zaborowski
2007-11-08 14:58       ` Avi Kivity [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=47332425.70109@qumranet.com \
    --to=avi@qumranet.com \
    --cc=qemu-devel@nongnu.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).