All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] make mc13783 code generic
Date: Tue, 30 Nov 2010 15:17:25 +0000	[thread overview]
Message-ID: <20101130151725.GN7403@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101130151540.GN20449@pengutronix.de>

On Tue, Nov 30, 2010 at 04:15:40PM +0100, Uwe Kleine-K?nig wrote:
> On Tue, Nov 30, 2010 at 02:55:17PM +0000, Mark Brown wrote:

> > interest in most of the code he's touching.  If you use the --nogit
> > option (which is the default with current -next) get_maintainer.pl is a
> > bit safer but you then need to think about people who might be actively

> I tried --nogit some time ago, but it still used git.  After looking
> again I probably should have passed --nogit-fallback, too.

Oh, erk - hadn't noticed the fallback stuff.  The general point we're
both making does still stand, get_maintainer is a useful starting point
but should never be considered gospel.

  reply	other threads:[~2010-11-30 15:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30  6:26 [PATCH] make mc13783 code generic Yong Shen
2010-11-30  9:12 ` Arnaud Patard (Rtp)
2010-11-30  9:47   ` Yong Shen
2010-12-02 14:28     ` Uwe Kleine-König
2010-12-03  6:34       ` Yong Shen
2010-11-30 14:35   ` Uwe Kleine-König
2010-11-30  9:41 ` Alberto Panizzo
2010-11-30  9:50   ` Yong Shen
2010-11-30 14:32   ` Uwe Kleine-König
2010-11-30 14:55     ` Mark Brown
2010-11-30 15:15       ` Uwe Kleine-König
2010-11-30 15:17         ` Mark Brown [this message]
2010-12-01  6:07           ` Yong Shen
  -- strict thread matches above, loose matches on Subject: below --
2010-11-30  6:11 Yong Shen

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=20101130151725.GN7403@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.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.