similar to: Remote protocol abstracted

For the last year we have been working hard in releasing an open source RESTful xapian server named Xapiand (https://github.com/Kronuz/Xapiand) that will offer clustering, replication and some other neat features (similar to what elasticsearch offers, but the final goals go beyond it); however, for our Xapiand server to work, we need to have a few changes in xapian-core that are **essential**.

Hi all, Many of the source files are moving towards having the property svn:eolstyle=native (thanks Richard!) In trying to keep up with bug 100, I've noticed (via "entire file is in conflict due to eol markers" diffs :) that the following files still lack this setting: xapian-core/matcher/Makefile.mk xapian-core/net/serialise.cc xapian-core/net/remoteserver.cc

Daniel, Tobias, Renato and myself have been looking a little bit at the potential underlying reason for why http://llvm.org/perf/ is instable, and have found some clues. I want to share them here to give people with more experience in the frameworks used by LNT (flask, sqlalchemy, wsgi, .) a chance to check if our reasoning below seems plausible. Daniel noticed the following backtrace in the

This patch series integrates libosinfo in virt-v2v to get the list of files for Windows from libosinfo, if possible. The actual data is still from virtio-win, just unpacked. Pino Toscano (3): build: require libosinfo v2v: add a minimal libosinfo interface v2v: try to get windows driver files from libosinfo m4/guestfs-v2v.m4 | 3 + v2v/Makefile.am | 9 +-

This patch series integrates libosinfo in virt-v2v to get the list of files for Windows from libosinfo, if possible. The actual data is still from virtio-win, just unpacked. Changes from v1: - adapt to use the priority in libosinfo 1.7.0+ - filter out non-pre-installable drivers - collect all the drivers matching the requirements, not just the first, sorting them by priority like libosinfo does