linux-kernel - Re: [PATCH] [545/2many] MAINTAINERS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Aug 2007 12:19:38 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Chris Wright <chrisw@...s-sol.org>, joe@...ches.com,
	xen-devel@...ts.xensource.com, virtualization@...ts.osdl.org,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	jeremy@...source.com, akpm@...ux-foundation.org
Subject: Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE

* Randy Dunlap (randy.dunlap@...cle.com) wrote:
> On Mon, 13 Aug 2007 11:55:36 -0700 Chris Wright wrote:
> > * joe@...ches.com (joe@...ches.com) wrote:
> > > +F:	arch/i386/xen/
> > > +F:	drivers/*/xen-*front.c
> > > +F:	drivers/xen/
> > > +F:	include/asm-i386/xen/
> > > +F:	include/xen/
> > 
> > I think this data will easily become stale.  What is the point again?
> 
> Agreed.  But not everyone wants to or should have to use git,
> so what are the alternatives?

Between git (or gitweb), existing MAINTAINERS and a bit of common
sense (or extra sleuthing), I never perceived a significant problem.
Alternative could be to place info directly in source files.  If not
all of MAINTAINERS info, it could be a tag to reference the relevant
MAINTAINERS entry.

thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/