On 22/03/2018 20:29, Michael S. Tsirkin wrote: > On Wed, Mar 21, 2018 at 05:22:03PM +0100, Kevin Wolf wrote: >>> It's all still very much a non-standard convention and so less robust >>> than prefixing file name with a project-specifix prefix. >> I've always had the impression that it's by far the most common >> convention, to the point that I'd blindly assume it when joining a new >> project. > > Any examples?
GCC - https://github.com/gcc-mirror/gcc/blob/master/gcc/reload.c Libvirt - https://github.com/libvirt/libvirt/blob/master/src/util/virprocess.c SDL - https://github.com/SDL-mirror/SDL/blob/master/src/core/unix/SDL_poll.c Anything but Linux really. I find <qemu/foo/bar.h> verbose and unnecessary. The only advantage of your proposal is that files included from the source directory would be clearly noticeable. That said, it's easy to add a checkpatch.pl rule that detects when ".../..." is used on a file not under include/. Paolo
