Re: [PATCH] [443/2many] MAINTAINERS - HIBERNATION (aka Software Suspend, aka swsusp):

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Tue, 14 Aug 2007, Joe Perches wrote:
>
> SUSPEND TO RAM:
> P:	Pavel Machek
> M:	pavel@xxxxxxx
> P:	Rafael J. Wysocki
> M:	rjw@xxxxxxx
> L:	linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
> S:	Maintained
> F:	Documentation/power/
> F:	arch/i386/kernel/acpi/
> F:	arch/x86_64/kernel/acpi/
> F:	arch/x86_64/kernel/suspend.c
> F:	drivers/base/power/
> F:	kernel/power/
> F:	include/linux/suspend.h
> F:	include/linux/freezer.h
> F:	include/linux/pm.h
> F:	include/asm-*/suspend.h

Quite frankly, I think the MAINTAINERS file gets a whole lot uglier this 
way.

There's also a rather fundamental issue: this will likely make people 
touch the MAINTAINERS file *more*, and from a maintenance standpoint, that 
is exactly the wrong thing to have (one central file that everybody 
touches). It just tends to generate unnecessary merge conflicts etc. 

(We used to have that issue with the central configuration file, for 
example).

So the more I look at these things, the more convinced I am that this is 
not the right thing to do. These things should *not* be in one huge file, 
and I'd much much rather have the maintainership information be carried 
along with the subsystem itself, or the files it contains.

In other words, it would be much better to just have per-file markers, 
along with some per-subdirectory stuff or similar.

			Linus
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux