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é <[email protected]> > 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 :|
