linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: 46dcfc8 (ARM: Update mach-types) removes used machine types
Date: Mon, 22 Aug 2011 15:36:12 +0200	[thread overview]
Message-ID: <201108221536.12859.marek.vasut@gmail.com> (raw)
In-Reply-To: <20110822133242.GE2287@n2100.arm.linux.org.uk>

On Monday, August 22, 2011 03:32:42 PM Russell King - ARM Linux wrote:
> On Mon, Aug 22, 2011 at 03:30:41PM +0200, Marek Vasut wrote:
> > On Monday, August 22, 2011 03:27:19 PM Russell King - ARM Linux wrote:
> > > On Mon, Aug 22, 2011 at 03:16:00PM +0200, Marek Vasut wrote:
> > > > On Monday, August 22, 2011 03:01:19 PM Russell King - ARM Linux wrote:
> > > > > For further reading, see:
> > > > > http://lists.arm.linux.org.uk/lurker/message/20110815.085325.ae6ee0
> > > > > 7d.e n.ht ml
> > > > 
> > > > Russell, calm down please.
> > > > 
> > > > Maybe it'd be better to just email the people with broken stuff, then
> > > > wait ... if they don't reply in a week (two weeks?) then remove their
> > > > stuff. And make that a policy.
> > > > 
> > > > What do you think ?
> > > 
> > > Who do I email?  Which entries are causing problems?  That's the whole
> > > bloody point.
> > 
> > Isn't the email in your database? You can't just script that ?
> > 
> > > There's just far too much of it.  The amount of effort required to sort
> > > through this file each time it needs to be updated has become
> > > *excessive*. The amount of effort required to go through the file and
> > > identify which entries are broken is *excessive*.  The amount of
> > > effort required to find who to email is *excessive*.
> > 
> > Why not write a script for that ?
> 
> No, I don't have the time at present.

You're the head maintainer here and ARM is a rising architecture. If you can't 
cope with that, you have a growing community of very competent people here. 
Maybe someone will be willing to take over eventually? It'll relieve some 
pressure from you too, what do you think?

  reply	other threads:[~2011-08-22 13:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22  8:10 46dcfc8 (ARM: Update mach-types) removes used machine types Uwe Kleine-König
2011-08-22  8:17 ` Russell King - ARM Linux
2011-08-22  8:33   ` Uwe Kleine-König
2011-08-22 11:18     ` Marek Vasut
2011-08-22 12:49       ` Russell King - ARM Linux
2011-08-22 12:54         ` Marek Vasut
2011-08-22 12:56           ` Russell King - ARM Linux
2011-08-22 13:01             ` Russell King - ARM Linux
2011-08-22 13:16               ` Marek Vasut
2011-08-22 13:27                 ` Russell King - ARM Linux
2011-08-22 13:30                   ` Marek Vasut
2011-08-22 13:32                     ` Russell King - ARM Linux
2011-08-22 13:36                       ` Marek Vasut [this message]
2011-08-22 13:48                         ` Russell King - ARM Linux
2011-08-22 14:09                           ` Eric Miao
2011-08-22 13:04             ` Eric Bénard
2011-08-22 13:55               ` Russell King - ARM Linux
2011-08-22 14:19                 ` [PATCH] cpuimx* boards: fix mach-types errors Eric Bénard
2011-08-22 14:37                   ` Russell King - ARM Linux
2011-08-22 14:43                     ` Eric Bénard
2011-08-22 12:55         ` 46dcfc8 (ARM: Update mach-types) removes used machine types Russell King - ARM Linux

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=201108221536.12859.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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 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).