On 05/09/2018 03:11 PM, John Ferlan wrote:
>
>
> On 05/09/2018 04:57 AM, Daniel P. Berrangé wrote:
>> On Wed, May 09, 2018 at 10:46:19AM +0200, Jiri Denemark wrote:
>>> On Tue, May 08, 2018 at 14:07:31 +0100, Daniel P. Berrangé wrote:
Currently all patches are simply sent to the main libvirt
On 05/09/2018 04:57 AM, Daniel P. Berrangé wrote:
> On Wed, May 09, 2018 at 10:46:19AM +0200, Jiri Denemark wrote:
>> On Tue, May 08, 2018 at 14:07:31 +0100, Daniel P. Berrangé wrote:
>>> Currently all patches are simply sent to the main libvirt development
>>> mailing list. Sometimes individual
On Wed, May 09, 2018 at 10:46:19AM +0200, Jiri Denemark wrote:
> On Tue, May 08, 2018 at 14:07:31 +0100, Daniel P. Berrangé wrote:
> > Currently all patches are simply sent to the main libvirt development
> > mailing list. Sometimes individual developers are also CC'd but this is
> > typically the
On Tue, May 08, 2018 at 02:07:31PM +0100, Daniel P. Berrangé wrote:
Currently all patches are simply sent to the main libvirt development
mailing list. Sometimes individual developers are also CC'd but this is
typically the exception.
Libvirt does not follow a subsystem maintainer model, so ther
On Tue, May 08, 2018 at 14:07:31 +0100, Daniel P. Berrangé wrote:
> Currently all patches are simply sent to the main libvirt development
> mailing list. Sometimes individual developers are also CC'd but this is
> typically the exception.
>
> Libvirt does not follow a subsystem maintainer model, s
Currently all patches are simply sent to the main libvirt development
mailing list. Sometimes individual developers are also CC'd but this is
typically the exception.
Libvirt does not follow a subsystem maintainer model, so there is no
notion of owners for the different areas of code, but there ce
