From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@suse.de>
Cc: David Miller <davem@davemloft.net>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] split up feature-removal-schedule.txt
Date: Wed, 13 Feb 2008 09:33:15 -0800 [thread overview]
Message-ID: <1202923995.3129.26.camel@localhost> (raw)
In-Reply-To: <20080213165924.GB10129@suse.de>
On Wed, 2008-02-13 at 08:59 -0800, Greg KH wrote:
> > I suggest the same for MAINTAINERS
> Why, is it a merge problem for you?
$ git-log --pretty=oneline --name-only | \
grep -vP "[a-fA-F0-9]{40,40}\s" | sort | uniq -c | sort -rbn
541 MAINTAINERS
506 kernel/sched.c
374 drivers/scsi/libata-core.c
343 include/linux/sched.h
340 include/linux/libata.h
327 drivers/net/tg3.c
327 drivers/net/sky2.c
309 mm/page_alloc.c
304 drivers/ata/libata-core.c
296 Makefile
MAINTAINERS is the most frequently patched file
It's not kept in alphabetic order
It's not easy to find the appropriate maintainer for a specific file
I'd like to add file patterns to MAINTAINERS entries
next prev parent reply other threads:[~2008-02-13 17:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 7:02 [GIT PATCH] split up feature-removal-schedule.txt Greg KH
2008-02-13 7:04 ` David Miller
2008-02-13 7:22 ` Joe Perches
2008-02-13 16:18 ` Randy Dunlap
2008-02-13 16:59 ` Greg KH
2008-02-13 17:33 ` Joe Perches [this message]
2008-02-13 17:47 ` Greg KH
2008-02-13 18:13 ` Linus Torvalds
2008-02-13 18:19 ` Linus Torvalds
2008-02-13 23:38 ` Junio C Hamano
2008-02-13 19:32 ` Andrew Morton
2008-02-19 19:07 ` Greg KH
2008-02-19 19:34 ` Randy Dunlap
2008-02-19 19:49 ` Greg KH
2008-02-19 20:06 ` Adrian Bunk
2008-02-13 7:27 ` KOSAKI Motohiro
2008-02-13 10:30 ` [GIT PATCH] " Pekka Pietikainen
2008-02-13 17:00 ` Greg KH
2008-02-13 12:11 ` Jeff Garzik
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=1202923995.3129.26.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.