LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Joe Perches <joe@perches.com>
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:47:59 -0800	[thread overview]
Message-ID: <20080213174759.GB19653@suse.de> (raw)
In-Reply-To: <1202923995.3129.26.camel@localhost>

On Wed, Feb 13, 2008 at 09:33:15AM -0800, Joe Perches wrote:
> 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

But does it cause merge conflicts?  The size of it lends itself to no
real conflicts that I have run into over time, but others might have had
problems, that's why I'm asking.

> It's not kept in alphabetic order

You can send patches to fix this :)

> It's not easy to find the appropriate maintainer for a specific file

git does a better job of this at times :)

> I'd like to add file patterns to MAINTAINERS entries

I thought we had gone over this before...

thanks,

greg k-h

  reply	other threads:[~2008-02-13 17:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  7:02 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
2008-02-13 17:47         ` Greg KH [this message]
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=20080213174759.GB19653@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PATCH] split up feature-removal-schedule.txt' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).