mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Joe Perches <joe@perches.com>,
	mingo@elte.hu, linux-kernel@vger.kernel.org,
	ksummit-2010-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
Date: Tue, 31 Aug 2010 13:23:08 -0400	[thread overview]
Message-ID: <1283275388.1377.216.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20100826093838.74ab9958@infradead.org>

On Thu, 2010-08-26 at 09:38 -0700, 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.

We could add a toplevel "todo/" directory, with each project file in it
and a list of things todo. When the todo is done, that same commit could
remove the todo item.

Just a worthless thought ;-)

-- Steve



  parent reply	other threads:[~2010-08-31 17:23 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 15:45 Paul E. McKenney
2010-08-26 15:51 ` Jiri Kosina
2010-08-26 16:03   ` [PATCH] MAINTAINERS: add W: todo lists Joe Perches
2010-08-26 15:51 ` [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list Joe Perches
2010-08-26 16:14   ` Paul E. McKenney
2010-08-26 16:18     ` Joe Perches
2010-08-26 16:25     ` [Ksummit-2010-discuss] " James Bottomley
2010-08-26 16:29       ` Randy Dunlap
2010-08-26 16:34         ` James Bottomley
2010-08-26 16:38         ` Arjan van de Ven
2010-08-26 16:42           ` Jiri Kosina
2010-08-26 17:00             ` Dmitry Torokhov
2010-08-31 17:23           ` Steven Rostedt [this message]
2010-08-31 23:02             ` Paul E. McKenney
2010-08-31 23:17               ` Steven Rostedt
2010-08-31 23:19                 ` Rafael J. Wysocki
2010-08-31 23:25                 ` Luck, Tony
2010-08-31 23:46                   ` Joe Perches
2010-09-01  0:23                     ` Eric Paris
2010-09-01  0:34                       ` Joe Perches
2010-09-01  8:54                         ` Mark Brown
2010-09-01 10:03                           ` Mike Rapoport
2010-09-01 10:15                             ` Mark Brown
2010-09-01 10:02                       ` Alan Cox
2010-08-27  9:19         ` Avi Kivity
2010-08-26 16:30       ` Joe Perches
2010-08-26 16:45       ` Joe Perches
2010-08-26 16:50       ` Paul E. McKenney
2010-08-26 23:00         ` Sarah Sharp
2010-08-26 23:23           ` Paul E. McKenney
2010-08-30  1:40             ` Neil Brown
2010-08-30 15:19               ` Eric Van Hensbergen
2010-08-26 23:30           ` Joe Perches
2010-08-26 20:47 ` [rfc] MAINTAINERS: Remove broken URLs Joe Perches
2010-08-26 20:49   ` Roland Dreier
2010-08-26 22:28   ` Justin P. Mattock
2010-08-26 22:37     ` Joe Perches
2010-08-26 22:45       ` Justin P. Mattock
2010-08-26 22:38   ` rdunlap
2010-08-27 13:46   ` John W. Linville

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1283275388.1377.216.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=arjan@infradead.org \
    --cc=joe@perches.com \
    --cc=ksummit-2010-discuss@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®