[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200708130024.23968.david-b@pacbell.net>
Date: Mon, 13 Aug 2007 00:24:23 -0700
From: David Brownell <david-b@...bell.net>
To: joe@...ches.com
Cc: linux-usb-devel@...ts.sourceforge.net,
torvalds@...ux-foundation.org,
linux-usb-users@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, johannes@...felt.com,
akpm@...ux-foundation.org
Subject: Re: [linux-usb-devel] [PATCH] [497/2many] MAINTAINERS - USB HUB DRIVER
On Sunday 12 August 2007, joe@...ches.com wrote:
> Add file pattern to MAINTAINER entry
>
> Signed-off-by: Joe Perches <joe@...ches.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists