On 08/08/2017 07:00 PM, Scott Garfinkle wrote: > I think this may have gotten lost in the 3.6 release. Does someone have > the time to review this, please? "Typically" in order to get someone to review a series that hasn't been looked at you should reply-all to the .0 cover-letter (or just the single patch) with a "ping" in the first few lines (e.g. a top post). Getting a review is generally a factor of time for "commit reviewers" to review patches and "availability" of someone that knows the space with a "side" of whether that someone may also be "on vacation" ;-). Another factor to consider - I know it's a v3, but patches generated for new code at the end of the month (e.g., this series was 7/28) during a freeze (started on 7/27) won't get looked at until the following month. I'll look at the series this week, but I also suspect Jiri who looked at your v2 may have some comments, but he's out of the office for a bit longer... Others may have comments too, but usually when we all see migrate we hope for Jiri to have a look! > > The patches still apply cleanly (albeit with fuzz) at the current level. They applied cleanly for me today for my review branch - no lint brush necessary ;-) John > > -Scott Garfinkle > > > -- > libvir-list mailing list > libvir-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/libvir-list -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
