From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Glauber Costa <glommer@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
armbru@redhat.com
Subject: Re: [Qemu-devel] sending pci information over the wire
Date: Fri, 19 Jun 2009 15:47:39 +0100 [thread overview]
Message-ID: <200906191547.41173.paul@codesourcery.com> (raw)
In-Reply-To: <4A3BA1C6.6040701@redhat.com>
> Also it seems for merges only a message for the merge commit goes to
> the list, not for the individual patches.
This depends how the merge is done. A few of the recent merges did not rebase
the changes before comitting. This leads to nonlinear revision history, as can
easily be seen with e.g. .gitk e510e05b
Paul
next prev parent reply other threads:[~2009-06-19 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 19:39 [Qemu-devel] sending pci information over the wire Glauber Costa
2009-06-18 20:03 ` Anthony Liguori
2009-06-18 20:12 ` Glauber Costa
2009-06-18 20:38 ` Anthony Liguori
2009-06-19 8:55 ` Gerd Hoffmann
2009-06-19 13:10 ` Anthony Liguori
2009-06-19 14:33 ` Gerd Hoffmann
2009-06-19 14:47 ` Paul Brook [this message]
2009-06-19 15:16 ` Anthony Liguori
2009-06-19 15:38 ` Gerd Hoffmann
2009-06-19 15:56 ` Anthony Liguori
2009-06-20 18:58 ` 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=200906191547.41173.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=armbru@redhat.com \
--cc=glommer@redhat.com \
--cc=kraxel@redhat.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).