From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com, anthony@codemonkey.ws,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PULL 0/1] MAINTAINERS update for 0.15
Date: Thu, 22 Aug 2013 19:30:45 +0200 [thread overview]
Message-ID: <1377192646-4425-1-git-send-email-afaerber@suse.de> (raw)
Hello Anthony,
Here's a pull for the patch that was sent to document me as 0.15 maintainer
back in 2012 [1], which I had been doing until late 2012 when things started
to stall upstream. Doing this as a pull preserves the patch date rather than
using the resend date; cherry-pick -s would also work of course.
Once my upcoming pull transferring qemu-stable-0.15.git to qemu.git stable-0.15
(authorized by this MAINTAINERS change) has been applied, we can follow up
with deleting the T: git git://git.qemu.org/qemu-stable-x.y.git entries.
Regards,
Andreas
[1] http://patchwork.ozlabs.org/patch/152873/
The following changes since commit ecfe10c9a6f9bc77d0e4b7eb5d0f5d61e8fbaed8:
Merge remote-tracking branch 'pmaydell/tags/pull-target-arm-20130820' into staging (2013-08-20 11:23:52 -0500)
are available in the git repository at:
git://github.com/afaerber/qemu-cpu.git tags/0.15-maintainer-for-anthony
for you to fetch changes up to 73c30df69ce1f6767a7dba29b2411329de102847:
MAINTAINERS: Take over 0.15 maintenance (2013-08-22 17:27:43 +0200)
----------------------------------------------------------------
MAINTAINERS update for stable-0.15
----------------------------------------------------------------
Andreas Färber (1):
MAINTAINERS: Take over 0.15 maintenance
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2013-08-22 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 17:30 Andreas Färber [this message]
2013-08-22 17:30 ` [Qemu-devel] [PULL 1/1] MAINTAINERS: Take over 0.15 maintenance Andreas Färber
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=1377192646-4425-1-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=mdroth@linux.vnet.ibm.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).