From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: KVM call agenda for Mars 21th
Date: Mon, 21 Mar 2011 13:58:35 +0100 [thread overview]
Message-ID: <m3wrjszl38.fsf@neno.mitica> (raw)
Please, send in any agenda items you are interested in covening.
- Merge patches speed. I just "feel", that patches are not being
handled fast enough, so ... I looked how much patches have been
integrated since Mars 1st:
(master)$ g log --pretty=fuller ed02c54d1fd5d35c06e62e3dae84ee5bb90097ef.. | grep "^Commit: " | wc -l
121
121 patches total.
Now, I looked at how much patches Anthony commited himself:
(master)$ g log --pretty=fuller ed02c54d1fd5d35c06e62e3dae84ee5bb90097ef.. | grep "^Commit: " | grep Anthony | wc -l
13
This feel pretty bad, having in account that I have almost 80 patches
on the list waiting for action. As it "appears" that more people is
also waiting for Anthony to merge things, I think we have a problem
here.
And no, I don't want to make Anthony feel bad, but I know that the kind
of patches that I sent are for subsystems that only he merges. I think
that we really have a problem integrating patches, it just takes too
long.
Thanks, Juan.
next reply other threads:[~2011-03-21 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 12:58 Juan Quintela [this message]
2011-03-22 13:03 ` [Qemu-devel] KVM call agenda for Mars 21th Luiz Capitulino
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=m3wrjszl38.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=kvm@vger.kernel.org \
--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