Re: [libvirt] [PATCH 05/10] daemon: move libvirtd code into src/remote/ directory

2018-02-22 Thread Daniel P . Berrangé
On Thu, Feb 22, 2018 at 11:24:24AM +0100, Michal Privoznik wrote: > On 02/21/2018 04:35 PM, Daniel P. Berrangé wrote: > > Having a daemon/ directory makes little sense from a code structure > > point of view, as 90% of the code that is built into libvirtd already > > lives in the src/ directory. Th

Re: [libvirt] [PATCH 05/10] daemon: move libvirtd code into src/remote/ directory

2018-02-22 Thread Michal Privoznik
On 02/21/2018 04:35 PM, Daniel P. Berrangé wrote: > Having a daemon/ directory makes little sense from a code structure > point of view, as 90% of the code that is built into libvirtd already > lives in the src/ directory. The virtlockd and virlogd daemons also live > entirely in src/{locking,loggi

[libvirt] [PATCH 05/10] daemon: move libvirtd code into src/remote/ directory

2018-02-21 Thread Daniel P . Berrangé
Having a daemon/ directory makes little sense from a code structure point of view, as 90% of the code that is built into libvirtd already lives in the src/ directory. The virtlockd and virlogd daemons also live entirely in src/{locking,logging} directories. This moves the source code for libvirtd i