All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: alphabetic ordering of MAINTAINERS
Date: Fri, 4 Jul 2008 08:41:22 +0200	[thread overview]
Message-ID: <20080704064122.GA14806@digi.com> (raw)
In-Reply-To: <20080704063938.GA12894@uranus.ravnborg.org>

Sam Ravnborg wrote:
> On Fri, Jul 04, 2008 at 08:34:55AM +0200, Uwe Kleine-König wrote:
> > Hello,
> >
> > I wanted to add an entry to MAINTAINERS and while doing it I saw that in
> > the corresponding region the alphabetic ordering is broken.  Then I
> > inteded to fix that up for a trivial patch.  Next was to check the rest
> > of the file and there are so much misorderings that it's not sensible to
> > choose the trivial path anymore as there are currently 114 entries out
> > of order[1].
> >
> > Below is a script that shows the misorderings after applying the
> > following patch:
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index e6c06fa..e9e36f8 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1585,7 +1585,7 @@ S:      Supported
> >  EMBEDDED LINUX
> >  P:   Paul Gortmaker
> >  M:   paul.gortmaker@windriver.com
> > -P    David Woodhouse
> > +P:   David Woodhouse
> >  M:   dwmw2@infradead.org
> >  L:   linux-embedded@vger.kernel.org
> >  S:   Maintained
> >
> > IMHO there are two good ways to continue:
> >  - just ignore the misorderings; or
> >  - write a more clever script that not only shows the misorderings but
> >    fixes them and optimally let Linus directly apply it.
> >
> > I will try to come up with a script to prepare the second way.
> 
> If you succeed doing so it would be very good to fix up
> all mail entries to read:
> 
> M: Paul Gortmaker <paul.gortmaker@windriver.com>
> 
> so they are copy'n'paste friendly.
IMHO this would be a second step, but I like it.

Best regards
Uwe

-- 
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962

  reply	other threads:[~2008-07-04  6:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  6:34 alphabetic ordering of MAINTAINERS Uwe Kleine-König
2008-07-04  6:39 ` Sam Ravnborg
2008-07-04  6:41   ` Uwe Kleine-König [this message]
2008-07-04  6:52 ` Oliver Neukum
2008-07-04  6:57   ` Uwe Kleine-König
2008-07-04  8:59     ` Paul Mundt
2008-07-04  9:10       ` Uwe Kleine-König
2008-07-04 12:07         ` Alan Cox
2008-07-04 14:02           ` Uwe Kleine-König
2008-07-04 12:02   ` Bernd Petrovitsch
2008-07-04 12:06     ` Oliver Neukum
2008-07-04 12:34   ` [RFC] MAINTAINERS service, was: " Krzysztof Halasa
2008-07-04 13:44     ` Uwe Kleine-König
2008-07-04 14:08       ` Krzysztof Halasa
2008-07-07 13:19         ` Stefan Richter
2008-07-07 18:52           ` Krzysztof Halasa
2008-07-07 19:18             ` Stefan Richter
2008-07-07 22:37               ` Krzysztof Halasa
2008-07-07 23:33                 ` Stefan Richter
2008-07-09 20:14     ` Pavel Machek
2008-07-09 20:11   ` Pavel Machek
2008-07-04  8:50 ` Uwe Kleine-König

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=20080704064122.GA14806@digi.com \
    --to=uwe.kleine-koenig@digi.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.