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:	Thu, 26 Aug 2010 18:42:55 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Randy Dunlap <rdunlap@...otime.net>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	Joe Perches <joe@...ches.com>, mingo@...e.hu,
	linux-kernel@...r.kernel.org,
	ksummit-2010-discuss@...ts.linux-foundation.org
Subject: Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of
 todo list, add RCU todo list

On Thu, 26 Aug 2010, Arjan van de Ven wrote:

> I have to say that I'm not yet convinced that keeping a todo list in a 
> place that's not with the actual source code does not give me warm fuzzy 
> feelings. Every time we've kept information about the source code 
> separate from our source code it's been a failure; it gets out of sync 
> fast and it just adds to the maintenance.
> 
> A git commit that both fixes an issue and removed the line from the todo 
> file (or moves it to a "done" section, whatever) is the ultimate goal 
> obviously... having a U: seems to go in exactly the opposite direction.
> 
> otoh having a kernel-doc type (eg structured, parsable) way of
> gathering todo items throughout the tree.... that I can see as useful.

I still feel that if maintainer is willing to keep TODO list on web for 
whatever reason (hyperlinks, nice tables, images, whatever), then he 
should be free to do so.

The U: (or whatever) tag in MAINTAINERS file still could point to file in 
the actual sources, in cases maintainer choses to have the list there, of 
course.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ