* Avi Kivity <avi@xxxxxxxxxx> wrote: > On 11/02/2009 12:07 PM, Ingo Molnar wrote: >>> Ingo, can you queue this on x86/entry? >>> >> Already done, tested and pushed out. > > Usually there is an ack from tip-bot? Yeah, the final, committed form of the patch (with small edits done in 99% of the cases) gets sent to the discussion thread on lkml and can be reviewed (and double checked) there. <plug> We use the tip-bot mechanism to: - increase transparency (every commit gets posted into the lkml thread it originates from), - avoid patch-bombing/spamming lkml every week/month with new patches, - it also makes the patch postings much more on-topic and easier to ignore for those who are not interested in a discussion, - it can also be used to fine-tune any workflow details - the specific timings can be seen in the discussion, missed or incorrectly queued patches can be identified, - new discussions/bugreports can be started based on that commit notification, on lkml. Developers and maintainers involved in the process absolutely love it as it visibly increases workflow reliability and transparency and increases the information density on lkml - you might want to consider something similar too, for kvm.git ;-) </plug> Should be in your mbox any minute. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
