mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: joe@perches.com
Cc: 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 00:24:23 -0700	[thread overview]
Message-ID: <200708130024.23968.david-b@pacbell.net> (raw)
In-Reply-To: <46bffc57.+VLVIUHqG3mGbW2w%joe@perches.com>

On Sunday 12 August 2007, joe@perches.com wrote:
> Add file pattern to MAINTAINER entry
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> 

I seem to be missing some context for these "2many" patches; and
don't really see any in the MARC archives either.  This seems like
about 600 patches out of the blue.  A lot for RC3, even if it is
"just" for the MAINTAINERS file.

Is the motivation here purely to make it easier to find out how to
report bugs and suggest improvements?  If so, that seems like only
one of many related issues ...

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.



  reply	other threads:[~2007-08-13 12:45 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 ` David Brownell [this message]
2007-08-13 14:16   ` [linux-usb-devel] " Stefan Richter

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=200708130024.23968.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --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®