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]
Message-ID: <20100826170058.GA6761@core.coreip.homeip.net>
Date:	Thu, 26 Aug 2010 10:00:58 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org,
	ksummit-2010-discuss@...ts.linux-foundation.org,
	Joe Perches <joe@...ches.com>, mingo@...e.hu
Subject: Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of
 todo list, add RCU todo list

On Thu, Aug 26, 2010 at 06:42:55PM +0200, Jiri Kosina wrote:
> 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.
> > 

TODO might disappear without implementation, if you decide that the idea
wasn't a good one after all.

> > 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.
>

Yep, I do not want to be restricted to updating TODO during merge window
only as the changes to the list are not likely to count as bugfixes ;)

-- 
Dmitry
--
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