From: Anthony Liguori <anthony@codemonkey.ws>
To: Glauber Costa <glommer@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [GIT PULL] Stable branch update
Date: Thu, 28 May 2009 07:54:50 -0500 [thread overview]
Message-ID: <4A1E899A.2000104@codemonkey.ws> (raw)
In-Reply-To: <20090528115331.GA30777@poweredge.glommer>
Glauber Costa wrote:
> Sure. The only reason I didn't is that none of them are backports
>
> They're all clean cherry picks.
>
Maybe a longer git listing then? For patches that I don't pull into
stable the first go around, there usually was a reason. Sometimes it's
just a mistake on my part but it would be helpful to have enough context
to have a proper discussion on the mailing list.
I ended up doing a fetch and then looked through each commit. That's
good for me, but for others wanting to participate it would be good to
have more info on the list.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-05-28 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 18:04 [Qemu-devel] [GIT PULL] Stable branch update Glauber Costa
2009-05-28 7:10 ` Anthony Liguori
2009-05-28 11:53 ` Glauber Costa
2009-05-28 12:54 ` Anthony Liguori [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=4A1E899A.2000104@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=glommer@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).