All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	pavel@ucw.cz
Subject: Re: [PATCH 0/8] MAINTAINERS - add script and patterns
Date: Tue, 31 Mar 2009 14:24:08 -0700	[thread overview]
Message-ID: <1238534648.9715.306.camel@localhost> (raw)
In-Reply-To: <20090330135315.a05854da.akpm@linux-foundation.org>

On Mon, 2009-03-30 at 13:53 -0700, Andrew Morton wrote:
> Will that be OK?  Will the tool still work OK is MAITNAINERS is a bit
> wrong?

More or less.  By default it will still use git
"-by:" signers.  More pattern coverage is better.

> Is the tool capable of detecting misformatted MAINTAINERS entries?  If
> so, that would help long-term maintenance a lot.

Not really.

The MAINTAINERS file format is weakly specified.

I have a separate script that looks for patterns
that have no file matches and sections that have
no patterns.

Any suggestions?

btw: I did not do any patterns for ARM or PowerPC.
Of course those could be added in the future.

> I never have seen [patch 2/8] because the linux-foundation mail server
> thinks it's spam.

Actually, if the mail server is to be believed, the
MAINTAINERS file already contains a SPAM URI and
could be rejected if you sent it to yourself as-is.

On Tue, 2009-03-17 at 15:22 -0800, Mail Delivery Subsystem wrote:
>    ----- The following addresses...
> <torvalds@linux-foundation.org>
> <akpm@linux-foundation.org>
> 
>    ----- Transcript of session follows -----
> ... while talking to smtp1.linux-foundation.org.:
> >>> DATA
> <<< 451 4.3.2 Please try again later
> ... while talking to smtp2.linux-foundation.org.:
> >>> DATA
> <<< 554 5.7.1 Email body contains Spam URI
> 554 <akpm@linux-foundation.org>,<torvalds@linux-foundation.org>... Service unavailable

> So if all the above looks OK then please resend
> everything (yet again) to akpm@kernel.org.

Do you want me to wait for RC1 when most of the
MAINTAINERS changes should be done or do you want
it now?



  parent reply	other threads:[~2009-03-31 21:25 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
2009-03-30 21:29     ` Pavel Machek
2009-03-31  0:16   ` Arnd Bergmann
2009-03-31 21:24   ` Joe Perches [this message]
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=1238534648.9715.306.camel@localhost \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --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.