[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1283296622.1377.765.camel@gandalf.stny.rr.com>
Date: Tue, 31 Aug 2010 19:17:02 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: paulmck@...ux.vnet.ibm.com
Cc: Arjan van de Ven <arjan@...radead.org>,
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 Tue, 2010-08-31 at 16:02 -0700, Paul E. McKenney wrote:
> > 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 ;-)
>
> I am with Dmitry on this one. I really don't want to be prevented from
> updating my todo items outside of the merge window.
>
> Different people have different needs, so we need to accommodate todo
> lists both within and outside the kernel source tree.
Actually, that would probably happen automatically.
If you are working on a subsystem, you should probably be working
against the git tree for that subsystem. When something is done in the
todo list, the subsystem tree would be updated with the commit that does
said change.
Then, the list is maintained outside of mainline (in the subsystem git
tree) and will automatically update mainline in the next merge window
when the tree is pulled.
-- Steve
--
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