mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: David Brownell <david-b@pacbell.net>
Cc: joe@perches.com, linux-usb-devel@lists.sourceforge.net,
	torvalds@linux-foundation.org,
	linux-usb-users@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, johannes@erdfelt.com,
	akpm@linux-foundation.org
Subject: Re: [linux-usb-devel] [PATCH] [497/2many] MAINTAINERS - USB HUB DRIVER
Date: Mon, 13 Aug 2007 16:16:14 +0200	[thread overview]
Message-ID: <46C067AE.3090409@s5r6.in-berlin.de> (raw)
In-Reply-To: <200708130024.23968.david-b@pacbell.net>

David Brownell wrote:
> Is there general agreement that these "F:" entries should be used?
> Rather than, say, embedding references in the relevant parts of
> the source tree, adjacent to those files, where they would be more
> visible to people making relevant changes.
> 
> I'm also concerned with the reality that the MAINTAINERS file is
> not accurate.  The $SUBJECT patch is one example; the named maintainer
> is no longer active (in that area, at least) and the named driver is
> not actually separable from the rest of usbcore.  Better IMO to just
> remove the "hub driver" entry.

I don't speak for Joe, but:  If there is a good mapping from MAINTAINERS
to paths then more submitters will use MAINTAINERS more frequently.  A
side effect would be that outdated entries in MAINTAINERS would become
apparent more quickly, and updated more quickly.  Of course that's just
speculation --- but your comment on this "hub driver" entry, prompted by
Joe's patch, seems to support that speculation.
-- 
Stefan Richter
-=====-=-=== =--- -==-=
http://arcgraph.de/sr/

      reply	other threads:[~2007-08-13 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  6:38 joe
2007-08-13  7:24 ` [linux-usb-devel] " David Brownell
2007-08-13 14:16   ` Stefan Richter [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=46C067AE.3090409@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@linux-foundation.org \
    --cc=david-b@pacbell.net \
    --cc=joe@perches.com \
    --cc=johannes@erdfelt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=linux-usb-users@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®