On Fri, Jul 04, 2008 at 08:57:22AM +0200, Uwe Kleine-K?nig wrote:
quoted text
> Oliver Neukum wrote:
> > Am Freitag 04 Juli 2008 08:34:55 schrieb Uwe Kleine-K?nig:
> > > 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].
> > 
> > What good does alphabetic ordering? You'll grep it anyway.
> This is fine for me, too.  Then I suggest to remove the section
> 
> 	Note: For the hard of thinking, this list is meant to remain in alphabetical
> 	order. If you could add yourselves to it in alphabetical order that would be
> 	so much easier [Ed]
> 
> .  That's why I posted before spending time on writing a clever script.
> 
I always interpreted this to mean that the _entries_ are alphabetically
sorted, not the maintainers under each entry. IIRC, Alan has already
cleaned up most of the ordering of the entries through recent patches.

Historically the entries with multiple people listed have been in
decreasing order. Thus, the primary maintainer for a given entry is
listed first, with deputy maintainers following afterwards. Most places
where there are co-maintainers, there is still a single person who is the
main interface in to mainline, and it makes sense to have them listed
first. Re-ordering here would simply lead to confusion, or a lot of "send
this to xxx" mail. On the other hand, other entries with co-maintainers
tend to be more ad-hoc, so there doesn't seem to really be a good rule in
general. NETWORKING and KPROBES demonstrate both cases, as an example.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/