All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Marc Brekoo <m_brekoo@mailandnews.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Maintainers master list: new idea
Date: 06 Jul 2001 09:47:48 +0200	[thread overview]
Message-ID: <994405675.5488.2.camel@nomade> (raw)
In-Reply-To: <01e901c105a5$a0205220$0100a8c0@chello.nl>
In-Reply-To: <01e901c105a5$a0205220$0100a8c0@chello.nl>

I have another suggestion for the MAINTAINER list:

Put the filenames/directories the maintainer is responsible of, perhaps
in a hierarchical tree (X maintains usb drivers, Y maintains usb
keyboards, Z maintains usb keyboard from such vendor).
This should be coherent and easily parsable.

This way, someone which has to send several patches can make a little
script which finds the correct maintainers to send its stuff to.
I've already been in that situation, currently it's a pain.

Xav


  reply	other threads:[~2001-07-06  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05 22:52 [OT] Maintainers master list: new idea Marc Brekoo
2001-07-06  7:47 ` Xavier Bestel [this message]
2001-07-06 10:46   ` Marc Brekoo

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=994405675.5488.2.camel@nomade \
    --to=xavier.bestel@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m_brekoo@mailandnews.com \
    /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.