From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
pavel@ucw.cz
Subject: Re: [PATCH 0/8] MAINTAINERS - add script and patterns
Date: Mon, 30 Mar 2009 14:14:46 -0700 [thread overview]
Message-ID: <49D13646.5090000@oracle.com> (raw)
In-Reply-To: <20090330135315.a05854da.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Tue, 17 Mar 2009 16:19:21 -0700
> Joe Perches <joe@perches.com> wrote:
>
>> Add a script to find the maintainer of an individual
>> file or files in a patch and adds additional patterns
>> to MAINTAINERS.
>>
>> Other information from MAINTAINERS sections can
>> also be generated by file or patch.
>>
>> Signed-off-by: Joe Perches <joe@perches.com>
>
> gack, this isn't working out very well.
>
> Is everyone OK with the concept and execution? We think this is ready
> and desirable to merge?
I'm for it.
> I think I'd like this to sit in my tree for a while so I can have a
> play with it - I'm a major customer!
>
> The two problematic patches are the ones which make largish changes to
> the MAINTAINERS file, yes? One way to handle those is as a two-pass
> thing: I merge and maintain it as much as I can, but as people make
> additional changes and as the fixups get out of hand, the patch will
> end up only being 90% complete. So we'll need to do a later second
> pass to fix up the stragglers.
>
> Will that be OK? Will the tool still work OK is MAITNAINERS is a bit
> wrong?
>
> Is the tool capable of detecting misformatted MAINTAINERS entries? If
> so, that would help long-term maintenance a lot.
>
> I never have seen [patch 2/8] because the linux-foundation mail server
> thinks it's spam. So if all the above looks OK then please resend
> everything (yet again) to akpm@kernel.org. If/when the time comes I'll
> send it on to torvalds@kernel.org. If that person is redirecting his
> kernel.org email to linux-foundation.org then he presumably still
> won't receive it. We'll work it out at that time ;)
--
~Randy
next prev parent reply other threads:[~2009-03-30 21:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 23:19 [PATCH 0/8] MAINTAINERS - add script and patterns Joe Perches
2009-03-14 16:20 ` Pavel Machek
2009-03-17 23:19 ` [PATCH 1/8] Add scripts/get_maintainer.pl Joe Perches
2009-03-17 23:19 ` [PATCH 2/8] MAINTAINERS - Add file patterns Joe Perches
2009-03-17 23:19 ` [PATCH 3/8] MAINTAINERS - Standardize style Joe Perches
2009-03-17 23:19 ` [PATCH 4/8] MAINTAINERS - Remove HP Fibre Channel HBA no longer in tree Joe Perches
2009-03-17 23:19 ` [PATCH 5/8] MAINTAINERS - standardize "T: git urls" Joe Perches
2009-03-17 23:19 ` [PATCH 6/8] MAINTAINERS - Add Linus Torvalds' git Joe Perches
2009-03-17 23:19 ` [PATCH 7/8] MAINTAINERS - i2c_tiny_usb T: should be W: Joe Perches
2009-03-17 23:19 ` [PATCH 8/8] MAINTAINERS - Update FPU Emulator contact address and web page Joe Perches
2009-03-30 20:53 ` [PATCH 0/8] MAINTAINERS - add script and patterns Andrew Morton
2009-03-30 21:14 ` Randy Dunlap [this message]
2009-03-30 21:29 ` Pavel Machek
2009-03-31 0:16 ` Arnd Bergmann
2009-03-31 21:24 ` Joe Perches
2009-03-31 21:45 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2008-10-23 23:09 Joe Perches
2008-10-25 7:41 ` Pavel Machek
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=49D13646.5090000@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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.