From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] agents: Add a skill for finding your way around QEMU
Date: Thu, 3 Sep 2026 09:16:00 +0100 [thread overview]
Message-ID: <apkswHHNCXFL-s0R@redhat.com> (raw)
In-Reply-To: <CABgObfYDqp8ZPKXeh8WnxKooMPFhFP5A1qUbyaqzTjKKHAoehw@mail.gmail.com>
On Thu, Sep 03, 2026 at 10:10:59AM +0200, Paolo Bonzini wrote:
> On Thu, Sep 3, 2026 at 10:08 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
> > On Thu, Sep 03, 2026 at 09:36:56AM +0200, Paolo Bonzini wrote:
> > > +## Finding things
> > > +
> > > +`MAINTAINERS` is the authoritative map from file patterns to subsystems
> > > +and maintainers; use it to work out who owns code and which tree a
> > > +change goes through.
> >
> > Does the tree actually matter to agents or contributors sending patches ?
> > I would tend to say "use it to work out which maintainers to CC when
> > sending patches". The receiving maintainer(s) will decide which tree
> > it will go through.
>
> s/work out/suggest/ - since sending should still be a human act even
> with the proposal under discussion.
Or maybe we just instruct it to run 'get_maintainers.pl' to
work out the CC list ? That script is deterministic and thus
would not typically need human oversight, which will know will
often be skipped even if we require oversight in policy.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-09-03 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 7:36 [PATCH] agents: Add a skill for finding your way around QEMU Paolo Bonzini
2026-09-03 8:08 ` Daniel P. Berrangé
2026-09-03 8:10 ` Paolo Bonzini
2026-09-03 8:16 ` Daniel P. Berrangé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=apkswHHNCXFL-s0R@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.