From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, Soren Hansen <soren@ubuntu.com>
Subject: Re: [PATCH 1/3] Move common VGAState attributes to VGA_STATE_COMMON
Date: Sun, 24 Feb 2008 09:16:05 -0600 [thread overview]
Message-ID: <47C18A35.7080601@codemonkey.ws> (raw)
In-Reply-To: <47C12B74.9040100@qumranet.com>
Avi Kivity wrote:
> The trick to passing through patches is to have a
>
> From: Original Author <email@example.com>
>
> line in the beginning, which git picks up and uses to maintain
> authorship information. Also, sign-off normally. Acked-by means "I know
> the author" while Reviewed-by means "I know the author well".
>
Does From have to be the first line? git-send-email never seems to do
anything with From for me.
Regards,
Anthony Liguori
> Anyway I applied all these patches, including the vmware BAR patch since
> it's a dependency.
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-24 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 19:40 [PATCH] Don't explicitly set BAR values for VMware VGA Anthony Liguori
2008-02-22 19:40 ` [PATCH 1/3] Move common VGAState attributes to VGA_STATE_COMMON Anthony Liguori
2008-02-24 8:31 ` Avi Kivity
2008-02-24 15:16 ` Anthony Liguori [this message]
2008-02-24 15:38 ` Avi Kivity
2008-02-22 19:40 ` [PATCH 2/3] Factor out the VGA vram mapping updating routine Anthony Liguori
2008-02-22 19:40 ` [PATCH 3/3] Enable VGA optimization for VMware VGA Anthony Liguori
2008-02-22 22:29 ` [PATCH] Don't explicitly set BAR values " Anthony Liguori
2008-02-22 23:45 ` andrzej zaborowski
2008-02-23 0:03 ` Anthony Liguori
2008-02-23 1:02 ` andrzej zaborowski
2008-02-23 22:59 ` Anthony Liguori
2008-02-24 7:09 ` 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=47C18A35.7080601@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=soren@ubuntu.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