* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 16:25 ` [Ksummit-2010-discuss] " James Bottomley
@ 2010-08-26 16:29 ` Randy Dunlap
2010-08-26 16:34 ` James Bottomley
` (2 more replies)
2010-08-26 16:30 ` Joe Perches
` (2 subsequent siblings)
3 siblings, 3 replies; 40+ messages in thread
From: Randy Dunlap @ 2010-08-26 16:29 UTC (permalink / raw)
To: James Bottomley
Cc: paulmck, Joe Perches, mingo, linux-kernel, ksummit-2010-discuss
On Thu, 26 Aug 2010 11:25:33 -0500 James Bottomley wrote:
> On Thu, 2010-08-26 at 09:14 -0700, Paul E. McKenney wrote:
> > On Thu, Aug 26, 2010 at 08:51:44AM -0700, Joe Perches wrote:
> > > On Thu, 2010-08-26 at 08:45 -0700, Paul E. McKenney wrote:
> > > > Since T: and L: are already taken, add U: for URL of todo list.
> > > > Also add the RCU todo list to both the RCU and RCUTORTURE projects.
> > >
> > > Hi Paul
> > >
> > > I think W: already works perfectly well for this use.
> > >
> > > >From MAINTAINERS:
> > > W: Web-page with status/info
> > >
> > > > @@ -4801,6 +4802,7 @@ M: Josh Triplett <josh@freedesktop.org>
> > > > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > S: Supported
> > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > > F: Documentation/RCU/torture.txt
> > > > F: kernel/rcutorture.c
> > > >
> > > > @@ -4826,6 +4828,7 @@ M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > W: http://www.rdrop.com/users/paulmck/rclock/
> > > > S: Supported
> > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> >
> > OK, how about the following, then?
>
> Got to say I really think overloading W which means web page/status
> information isn't a very good idea:
>
> jejb@mulgrave:~/git/linux-2.6> grep -w 'W:' MAINTAINERS |wc -l
> 371
>
> We already have ~400 of them ... how's anyone looking for a todo list
> going to find the right one in amongst all the others (assuming a newbie
> with no subject predisposition simply trying to find any todo list).
Did you have an alternate suggestion?
Do you prefer a Grand Unified Todo List?
I don't mind the kernelnewbies list/location, but we need to give it
some TLC.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
^ permalink raw reply [flat|nested] 40+ messages in thread* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
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-27 9:19 ` Avi Kivity
2 siblings, 0 replies; 40+ messages in thread
From: James Bottomley @ 2010-08-26 16:34 UTC (permalink / raw)
To: Randy Dunlap; +Cc: Joe Perches, ksummit-2010-discuss, mingo, linux-kernel
On Thu, 2010-08-26 at 09:29 -0700, Randy Dunlap wrote:
> On Thu, 26 Aug 2010 11:25:33 -0500 James Bottomley wrote:
>
> > On Thu, 2010-08-26 at 09:14 -0700, Paul E. McKenney wrote:
> > > On Thu, Aug 26, 2010 at 08:51:44AM -0700, Joe Perches wrote:
> > > > On Thu, 2010-08-26 at 08:45 -0700, Paul E. McKenney wrote:
> > > > > Since T: and L: are already taken, add U: for URL of todo list.
> > > > > Also add the RCU todo list to both the RCU and RCUTORTURE projects.
> > > >
> > > > Hi Paul
> > > >
> > > > I think W: already works perfectly well for this use.
> > > >
> > > > >From MAINTAINERS:
> > > > W: Web-page with status/info
> > > >
> > > > > @@ -4801,6 +4802,7 @@ M: Josh Triplett <josh@freedesktop.org>
> > > > > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > > S: Supported
> > > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > > F: Documentation/RCU/torture.txt
> > > > > F: kernel/rcutorture.c
> > > > >
> > > > > @@ -4826,6 +4828,7 @@ M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > > W: http://www.rdrop.com/users/paulmck/rclock/
> > > > > S: Supported
> > > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > OK, how about the following, then?
> >
> > Got to say I really think overloading W which means web page/status
> > information isn't a very good idea:
> >
> > jejb@mulgrave:~/git/linux-2.6> grep -w 'W:' MAINTAINERS |wc -l
> > 371
> >
> > We already have ~400 of them ... how's anyone looking for a todo list
> > going to find the right one in amongst all the others (assuming a newbie
> > with no subject predisposition simply trying to find any todo list).
>
>
> Did you have an alternate suggestion?
New tag was fine ... kernelnewbies wiki is also fine. My point is that
if we're going to put them somewhere, lets make it obvious, not a find
the list type of exercise.
> Do you prefer a Grand Unified Todo List?
I already gave my opinion on that ...
James
> I don't mind the kernelnewbies list/location, but we need to give it
> some TLC.
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
> _______________________________________________
> Ksummit-2010-discuss mailing list
> Ksummit-2010-discuss@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/ksummit-2010-discuss
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
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-31 17:23 ` Steven Rostedt
2010-08-27 9:19 ` Avi Kivity
2 siblings, 2 replies; 40+ messages in thread
From: Arjan van de Ven @ 2010-08-26 16:38 UTC (permalink / raw)
To: Randy Dunlap
Cc: James Bottomley, Joe Perches, ksummit-2010-discuss, mingo,
linux-kernel
On Thu, 26 Aug 2010 09:29:23 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Thu, 26 Aug 2010 11:25:33 -0500 James Bottomley wrote:
>
> > On Thu, 2010-08-26 at 09:14 -0700, Paul E. McKenney wrote:
> > > On Thu, Aug 26, 2010 at 08:51:44AM -0700, Joe Perches wrote:
> > > > On Thu, 2010-08-26 at 08:45 -0700, Paul E. McKenney wrote:
> > > > > Since T: and L: are already taken, add U: for URL of todo
> > > > > list. Also add the RCU todo list to both the RCU and
> > > > > RCUTORTURE projects.
> > > >
> > > > Hi Paul
> > > >
> > > > I think W: already works perfectly well for this use.
> > > >
> > > > >From MAINTAINERS:
> > > > W: Web-page with status/info
> > > >
> > > > > @@ -4801,6 +4802,7 @@ M: Josh Triplett
> > > > > <josh@freedesktop.org> M: "Paul E. McKenney"
> > > > > <paulmck@linux.vnet.ibm.com> S: Supported
> > > > > T:
> > > > > git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > +U:
> > > > > http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > W:
> > > > http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > > F: Documentation/RCU/torture.txt
> > > > > F: kernel/rcutorture.c
> > > > >
> > > > > @@ -4826,6 +4828,7 @@ M: "Paul E. McKenney"
> > > > > <paulmck@linux.vnet.ibm.com> W:
> > > > > http://www.rdrop.com/users/paulmck/rclock/ S: Supported
> > > > > T:
> > > > > git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > +U:
> > > > > http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > W:
> > > > http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > OK, how about the following, then?
> >
> > Got to say I really think overloading W which means web page/status
> > information isn't a very good idea:
> >
> > jejb@mulgrave:~/git/linux-2.6> grep -w 'W:' MAINTAINERS |wc -l
> > 371
> >
> > We already have ~400 of them ... how's anyone looking for a todo
> > list going to find the right one in amongst all the others
> > (assuming a newbie with no subject predisposition simply trying to
> > find any todo list).
>
>
> Did you have an alternate suggestion?
>
> Do you prefer a Grand Unified Todo List?
>
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.
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
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
1 sibling, 1 reply; 40+ messages in thread
From: Jiri Kosina @ 2010-08-26 16:42 UTC (permalink / raw)
To: Arjan van de Ven
Cc: Randy Dunlap, James Bottomley, Joe Perches, mingo, linux-kernel,
ksummit-2010-discuss
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.
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 16:42 ` Jiri Kosina
@ 2010-08-26 17:00 ` Dmitry Torokhov
0 siblings, 0 replies; 40+ messages in thread
From: Dmitry Torokhov @ 2010-08-26 17:00 UTC (permalink / raw)
To: Jiri Kosina
Cc: Arjan van de Ven, linux-kernel, ksummit-2010-discuss, Joe Perches,
mingo
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
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 16:38 ` Arjan van de Ven
2010-08-26 16:42 ` Jiri Kosina
@ 2010-08-31 17:23 ` Steven Rostedt
2010-08-31 23:02 ` Paul E. McKenney
1 sibling, 1 reply; 40+ messages in thread
From: Steven Rostedt @ 2010-08-31 17:23 UTC (permalink / raw)
To: Arjan van de Ven
Cc: Randy Dunlap, James Bottomley, Joe Perches, mingo, linux-kernel,
ksummit-2010-discuss
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
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-31 17:23 ` Steven Rostedt
@ 2010-08-31 23:02 ` Paul E. McKenney
2010-08-31 23:17 ` Steven Rostedt
0 siblings, 1 reply; 40+ messages in thread
From: Paul E. McKenney @ 2010-08-31 23:02 UTC (permalink / raw)
To: Steven Rostedt
Cc: Arjan van de Ven, Randy Dunlap, James Bottomley, Joe Perches,
mingo, linux-kernel, ksummit-2010-discuss
On Tue, Aug 31, 2010 at 01:23:08PM -0400, Steven Rostedt wrote:
> 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 ;-)
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.
Thanx, Paul
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
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
0 siblings, 2 replies; 40+ messages in thread
From: Steven Rostedt @ 2010-08-31 23:17 UTC (permalink / raw)
To: paulmck
Cc: Arjan van de Ven, Randy Dunlap, James Bottomley, Joe Perches,
mingo, linux-kernel, ksummit-2010-discuss
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
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-31 23:17 ` Steven Rostedt
@ 2010-08-31 23:19 ` Rafael J. Wysocki
2010-08-31 23:25 ` Luck, Tony
1 sibling, 0 replies; 40+ messages in thread
From: Rafael J. Wysocki @ 2010-08-31 23:19 UTC (permalink / raw)
To: Steven Rostedt
Cc: paulmck, Arjan van de Ven, Randy Dunlap, James Bottomley,
Joe Perches, mingo, linux-kernel, ksummit-2010-discuss
On Wednesday, September 01, 2010, Steven Rostedt wrote:
> 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.
Seriously, given the known history of Documentation/feature-removal-schedule.txt,
I don't think this is going to work.
Thanks,
Rafael
^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
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
1 sibling, 1 reply; 40+ messages in thread
From: Luck, Tony @ 2010-08-31 23:25 UTC (permalink / raw)
To: Steven Rostedt, paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, James Bottomley,
ksummit-2010-discuss@lists.linux-foundation.org, Joe Perches,
mingo@elte.hu
>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.
But this would mean that the version of the todo list in Linus' tree
is usually a release (3 months) out of date. It would be a good idea
for a list maintained this way to include instructions on how to find
the current version, lest some unsuspecting person waste time working
on items that are already fixed and waiting for the next merge.
-Tony
^ permalink raw reply [flat|nested] 40+ messages in thread
* RE: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-31 23:25 ` Luck, Tony
@ 2010-08-31 23:46 ` Joe Perches
2010-09-01 0:23 ` Eric Paris
0 siblings, 1 reply; 40+ messages in thread
From: Joe Perches @ 2010-08-31 23:46 UTC (permalink / raw)
To: Luck, Tony
Cc: Steven Rostedt, paulmck@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, James Bottomley,
ksummit-2010-discuss@lists.linux-foundation.org, mingo@elte.hu
On Tue, 2010-08-31 at 16:25 -0700, Luck, Tony wrote:
> >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.
>
> But this would mean that the version of the todo list in Linus' tree
> is usually a release (3 months) out of date. It would be a good idea
> for a list maintained this way to include instructions on how to find
> the current version, lest some unsuspecting person waste time working
> on items that are already fixed and waiting for the next merge.
There are already reasonable mechanisms for this.
It's perfectly fine to have multiple T: entries,
one for a current tree, another for a -next tree.
SECTION - name
M: who <email.address>
T: git <url>
T: git <url-next>
F: dir/file_pattern
Linus rarely seems to object to pulling Documentation updates.
Note the Documentation updates after any -rc2
$ for ((i=25 ; i<36 ; i++)) ; do \
cv=v2.6.$i-rc2..v2.6.$i ; \
echo -n "$cv: " ; \
git log --pretty=oneline --no-merges $cv -- Documentation | wc -l; \
done
v2.6.25-rc2..v2.6.25: 87
v2.6.26-rc2..v2.6.26: 48
v2.6.27-rc2..v2.6.27: 65
v2.6.28-rc2..v2.6.28: 67
v2.6.29-rc2..v2.6.29: 50
v2.6.30-rc2..v2.6.30: 44
v2.6.31-rc2..v2.6.31: 35
v2.6.32-rc2..v2.6.32: 74
v2.6.33-rc2..v2.6.33: 31
v2.6.34-rc2..v2.6.34: 32
v2.6.35-rc2..v2.6.35: 8
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-31 23:46 ` Joe Perches
@ 2010-09-01 0:23 ` Eric Paris
2010-09-01 0:34 ` Joe Perches
2010-09-01 10:02 ` Alan Cox
0 siblings, 2 replies; 40+ messages in thread
From: Eric Paris @ 2010-09-01 0:23 UTC (permalink / raw)
To: Joe Perches
Cc: Luck, Tony, linux-kernel@vger.kernel.org,
ksummit-2010-discuss@lists.linux-foundation.org, mingo@elte.hu
On Tue, 2010-08-31 at 16:46 -0700, Joe Perches wrote:
> On Tue, 2010-08-31 at 16:25 -0700, Luck, Tony wrote:
> > >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.
> >
> > But this would mean that the version of the todo list in Linus' tree
> > is usually a release (3 months) out of date. It would be a good idea
> > for a list maintained this way to include instructions on how to find
> > the current version, lest some unsuspecting person waste time working
> > on items that are already fixed and waiting for the next merge.
>
> There are already reasonable mechanisms for this.
>
> It's perfectly fine to have multiple T: entries,
> one for a current tree, another for a -next tree.
If I just downloaded a big tar ball and started trolling randomly
through the source how am I going to know what the MAINTAINERS file is?
How am I going to know that todo entries should be located by opening
the magic file called MAINTAINERS, looking for T: entries, and then
checking out the listed web page?
random todo files scattered around the kernel, all with references that
might duplicate MAINTAINERS info, but which make it clear to a complete
newbie how development for that subsys works, seems simple and easy.
subsys maintainers might want to put all kinds of info in there, what
tree to develop against (rarely a tar ball of Linus' tree), pointers to
particularly relevant Documentation/ files, how they like to get
patches, where those patches usually end getting applied, what lists and
cc's to use, things like that.
I just think that hoping a newbie is going to naturally know MAINTAINERS
isn't the best.
-Eric
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
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:02 ` Alan Cox
1 sibling, 1 reply; 40+ messages in thread
From: Joe Perches @ 2010-09-01 0:34 UTC (permalink / raw)
To: Eric Paris
Cc: Luck, Tony, linux-kernel@vger.kernel.org,
ksummit-2010-discuss@lists.linux-foundation.org, mingo@elte.hu
On Tue, 2010-08-31 at 20:23 -0400, Eric Paris wrote:
> If I just downloaded a big tar ball and started trolling randomly
> through the source how am I going to know what the MAINTAINERS file is?
I think that tarball trolling is pretty rare these days.
Any one know the statistics for kernel git traffic vs tarballs?
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-09-01 0:34 ` Joe Perches
@ 2010-09-01 8:54 ` Mark Brown
2010-09-01 10:03 ` Mike Rapoport
0 siblings, 1 reply; 40+ messages in thread
From: Mark Brown @ 2010-09-01 8:54 UTC (permalink / raw)
To: Joe Perches
Cc: Eric Paris, Luck, Tony, linux-kernel@vger.kernel.org,
ksummit-2010-discuss@lists.linux-foundation.org, mingo@elte.hu
On Tue, Aug 31, 2010 at 05:34:17PM -0700, Joe Perches wrote:
> On Tue, 2010-08-31 at 20:23 -0400, Eric Paris wrote:
> > If I just downloaded a big tar ball and started trolling randomly
> > through the source how am I going to know what the MAINTAINERS file is?
> I think that tarball trolling is pretty rare these days.
My experience is that there's an awful lot of people working with
whatever kernel has been provided by their vendor rather than getting
kernels direct from kernel.org and they tend to only look as far as the
tarball (or other package) they got.
> Any one know the statistics for kernel git traffic vs tarballs?
The kernel.org traffic is going to miss people using distribution or
other non kernel.org traffic so might be a bit misleading.
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-09-01 8:54 ` Mark Brown
@ 2010-09-01 10:03 ` Mike Rapoport
2010-09-01 10:15 ` Mark Brown
0 siblings, 1 reply; 40+ messages in thread
From: Mike Rapoport @ 2010-09-01 10:03 UTC (permalink / raw)
To: Mark Brown
Cc: Joe Perches, Eric Paris, Luck, Tony, linux-kernel@vger.kernel.org,
ksummit-2010-discuss@lists.linux-foundation.org, mingo@elte.hu
On Wed, Sep 1, 2010 at 11:54 AM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Aug 31, 2010 at 05:34:17PM -0700, Joe Perches wrote:
>> On Tue, 2010-08-31 at 20:23 -0400, Eric Paris wrote:
>
>> > If I just downloaded a big tar ball and started trolling randomly
>> > through the source how am I going to know what the MAINTAINERS file is?
>
>> I think that tarball trolling is pretty rare these days.
>
> My experience is that there's an awful lot of people working with
> whatever kernel has been provided by their vendor rather than getting
> kernels direct from kernel.org and they tend to only look as far as the
> tarball (or other package) they got.
People that are working with vendor provided kernels do not tend to
contribute upstream. And those who want to contribute will find what
MAINTAINERS is.
>> Any one know the statistics for kernel git traffic vs tarballs?
>
> The kernel.org traffic is going to miss people using distribution or
> other non kernel.org traffic so might be a bit misleading.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Sincerely Yours,
Mike.
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-09-01 10:03 ` Mike Rapoport
@ 2010-09-01 10:15 ` Mark Brown
0 siblings, 0 replies; 40+ messages in thread
From: Mark Brown @ 2010-09-01 10:15 UTC (permalink / raw)
To: Mike Rapoport
Cc: Joe Perches, Eric Paris, Luck, Tony, linux-kernel@vger.kernel.org,
ksummit-2010-discuss@lists.linux-foundation.org, mingo@elte.hu
On Wed, Sep 01, 2010 at 01:03:07PM +0300, Mike Rapoport wrote:
> On Wed, Sep 1, 2010 at 11:54 AM, Mark Brown
> > My experience is that there's an awful lot of people working with
> > whatever kernel has been provided by their vendor rather than getting
> > kernels direct from kernel.org and they tend to only look as far as the
> > tarball (or other package) they got.
> People that are working with vendor provided kernels do not tend to
> contribute upstream. And those who want to contribute will find what
> MAINTAINERS is.
While the majority of people won't contribute upstream some do, or come
looking for support, and MAINTAINERS doesn't seem entirely reliable. I
think some people are expecting it to be for maintainers rather than a
list of them.
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-09-01 0:23 ` Eric Paris
2010-09-01 0:34 ` Joe Perches
@ 2010-09-01 10:02 ` Alan Cox
1 sibling, 0 replies; 40+ messages in thread
From: Alan Cox @ 2010-09-01 10:02 UTC (permalink / raw)
To: Eric Paris
Cc: Joe Perches, ksummit-2010-discuss@lists.linux-foundation.org,
mingo@elte.hu, linux-kernel@vger.kernel.org
> If I just downloaded a big tar ball and started trolling randomly
> through the source how am I going to know what the MAINTAINERS file is?
Probably because you started with Documentation/* which explains it in
SubmittingPatches for one ?
> I just think that hoping a newbie is going to naturally know MAINTAINERS
> isn't the best.
If they can't find the MAINTAINERS file in the top level directory, and
haven't read SubmittingPatches either then maybe that's not a complete
disaster at that point ?
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
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-27 9:19 ` Avi Kivity
2 siblings, 0 replies; 40+ messages in thread
From: Avi Kivity @ 2010-08-27 9:19 UTC (permalink / raw)
To: Randy Dunlap
Cc: James Bottomley, Joe Perches, ksummit-2010-discuss, mingo,
linux-kernel
On 08/26/2010 07:29 PM, Randy Dunlap wrote:
>
> Do you prefer a Grand Unified Todo List?
>
cat /sys/kernel/todo
cat /sys/module/*/todo
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 16:25 ` [Ksummit-2010-discuss] " James Bottomley
2010-08-26 16:29 ` Randy Dunlap
@ 2010-08-26 16:30 ` Joe Perches
2010-08-26 16:45 ` Joe Perches
2010-08-26 16:50 ` Paul E. McKenney
3 siblings, 0 replies; 40+ messages in thread
From: Joe Perches @ 2010-08-26 16:30 UTC (permalink / raw)
To: James Bottomley; +Cc: paulmck, mingo, linux-kernel, ksummit-2010-discuss
On Thu, 2010-08-26 at 11:25 -0500, James Bottomley wrote:
> We already have ~400 of them ... how's anyone looking for a todo list
> going to find the right one in amongst all the others (assuming a newbie
> with no subject predisposition simply trying to find any todo list).
Those folk might be better playing/practicing/honing skills
in staging where there already are TODO files.
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 16:25 ` [Ksummit-2010-discuss] " James Bottomley
2010-08-26 16:29 ` Randy Dunlap
2010-08-26 16:30 ` Joe Perches
@ 2010-08-26 16:45 ` Joe Perches
2010-08-26 16:50 ` Paul E. McKenney
3 siblings, 0 replies; 40+ messages in thread
From: Joe Perches @ 2010-08-26 16:45 UTC (permalink / raw)
To: James Bottomley; +Cc: paulmck, mingo, linux-kernel, ksummit-2010-discuss
On Thu, 2010-08-26 at 11:25 -0500, James Bottomley wrote:
> how's anyone looking for a todo list
> going to find the right one in amongst all the others (assuming a newbie
> with no subject predisposition simply trying to find any todo list).
$ find -name TODO | wc -l
40
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 16:25 ` [Ksummit-2010-discuss] " James Bottomley
` (2 preceding siblings ...)
2010-08-26 16:45 ` Joe Perches
@ 2010-08-26 16:50 ` Paul E. McKenney
2010-08-26 23:00 ` Sarah Sharp
3 siblings, 1 reply; 40+ messages in thread
From: Paul E. McKenney @ 2010-08-26 16:50 UTC (permalink / raw)
To: James Bottomley; +Cc: Joe Perches, mingo, linux-kernel, ksummit-2010-discuss
On Thu, Aug 26, 2010 at 11:25:33AM -0500, James Bottomley wrote:
> On Thu, 2010-08-26 at 09:14 -0700, Paul E. McKenney wrote:
> > On Thu, Aug 26, 2010 at 08:51:44AM -0700, Joe Perches wrote:
> > > On Thu, 2010-08-26 at 08:45 -0700, Paul E. McKenney wrote:
> > > > Since T: and L: are already taken, add U: for URL of todo list.
> > > > Also add the RCU todo list to both the RCU and RCUTORTURE projects.
> > >
> > > Hi Paul
> > >
> > > I think W: already works perfectly well for this use.
> > >
> > > >From MAINTAINERS:
> > > W: Web-page with status/info
> > >
> > > > @@ -4801,6 +4802,7 @@ M: Josh Triplett <josh@freedesktop.org>
> > > > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > S: Supported
> > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > > F: Documentation/RCU/torture.txt
> > > > F: kernel/rcutorture.c
> > > >
> > > > @@ -4826,6 +4828,7 @@ M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > W: http://www.rdrop.com/users/paulmck/rclock/
> > > > S: Supported
> > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> >
> > OK, how about the following, then?
>
> Got to say I really think overloading W which means web page/status
> information isn't a very good idea:
>
> jejb@mulgrave:~/git/linux-2.6> grep -w 'W:' MAINTAINERS |wc -l
> 371
>
> We already have ~400 of them ... how's anyone looking for a todo list
> going to find the right one in amongst all the others (assuming a newbie
> with no subject predisposition simply trying to find any todo list).
Hopefully the todo lists have "todo" or "TODO" in the URL. ;-)
Thanx, Paul
^ permalink raw reply [flat|nested] 40+ messages in thread* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
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-26 23:30 ` Joe Perches
0 siblings, 2 replies; 40+ messages in thread
From: Sarah Sharp @ 2010-08-26 23:00 UTC (permalink / raw)
To: Paul E. McKenney
Cc: James Bottomley, Joe Perches, ksummit-2010-discuss, mingo,
linux-kernel
On Thu, Aug 26, 2010 at 09:50:44AM -0700, Paul E. McKenney wrote:
> On Thu, Aug 26, 2010 at 11:25:33AM -0500, James Bottomley wrote:
> > On Thu, 2010-08-26 at 09:14 -0700, Paul E. McKenney wrote:
> > > On Thu, Aug 26, 2010 at 08:51:44AM -0700, Joe Perches wrote:
> > > > On Thu, 2010-08-26 at 08:45 -0700, Paul E. McKenney wrote:
> > > > > Since T: and L: are already taken, add U: for URL of todo list.
> > > > > Also add the RCU todo list to both the RCU and RCUTORTURE projects.
> > > >
> > > > Hi Paul
> > > >
> > > > I think W: already works perfectly well for this use.
> > > >
> > > > >From MAINTAINERS:
> > > > W: Web-page with status/info
> > > >
> > > > > @@ -4801,6 +4802,7 @@ M: Josh Triplett <josh@freedesktop.org>
> > > > > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > > S: Supported
> > > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > > F: Documentation/RCU/torture.txt
> > > > > F: kernel/rcutorture.c
> > > > >
> > > > > @@ -4826,6 +4828,7 @@ M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > > W: http://www.rdrop.com/users/paulmck/rclock/
> > > > > S: Supported
> > > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > >
> > > OK, how about the following, then?
> >
> > Got to say I really think overloading W which means web page/status
> > information isn't a very good idea:
> >
> > jejb@mulgrave:~/git/linux-2.6> grep -w 'W:' MAINTAINERS |wc -l
> > 371
> >
> > We already have ~400 of them ... how's anyone looking for a todo list
> > going to find the right one in amongst all the others (assuming a newbie
> > with no subject predisposition simply trying to find any todo list).
>
> Hopefully the todo lists have "todo" or "TODO" in the URL. ;-)
That may not be the case if you use a public todo list on
rememberthemilk.com. It doesn't make sense to end multiple todo list
names with "todo" for on site that's specifically designed to help with
todo lists.
I like the idea of a separate letter for todo lists URLs.
Sarah Sharp
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 23:00 ` Sarah Sharp
@ 2010-08-26 23:23 ` Paul E. McKenney
2010-08-30 1:40 ` Neil Brown
2010-08-26 23:30 ` Joe Perches
1 sibling, 1 reply; 40+ messages in thread
From: Paul E. McKenney @ 2010-08-26 23:23 UTC (permalink / raw)
To: Sarah Sharp
Cc: James Bottomley, Joe Perches, ksummit-2010-discuss, mingo,
linux-kernel
On Thu, Aug 26, 2010 at 04:00:21PM -0700, Sarah Sharp wrote:
> On Thu, Aug 26, 2010 at 09:50:44AM -0700, Paul E. McKenney wrote:
> > On Thu, Aug 26, 2010 at 11:25:33AM -0500, James Bottomley wrote:
> > > On Thu, 2010-08-26 at 09:14 -0700, Paul E. McKenney wrote:
> > > > On Thu, Aug 26, 2010 at 08:51:44AM -0700, Joe Perches wrote:
> > > > > On Thu, 2010-08-26 at 08:45 -0700, Paul E. McKenney wrote:
> > > > > > Since T: and L: are already taken, add U: for URL of todo list.
> > > > > > Also add the RCU todo list to both the RCU and RCUTORTURE projects.
> > > > >
> > > > > Hi Paul
> > > > >
> > > > > I think W: already works perfectly well for this use.
> > > > >
> > > > > >From MAINTAINERS:
> > > > > W: Web-page with status/info
> > > > >
> > > > > > @@ -4801,6 +4802,7 @@ M: Josh Triplett <josh@freedesktop.org>
> > > > > > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > > > S: Supported
> > > > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > > >
> > > > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > > >
> > > > > > F: Documentation/RCU/torture.txt
> > > > > > F: kernel/rcutorture.c
> > > > > >
> > > > > > @@ -4826,6 +4828,7 @@ M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > > > W: http://www.rdrop.com/users/paulmck/rclock/
> > > > > > S: Supported
> > > > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > > >
> > > > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > >
> > > > OK, how about the following, then?
> > >
> > > Got to say I really think overloading W which means web page/status
> > > information isn't a very good idea:
> > >
> > > jejb@mulgrave:~/git/linux-2.6> grep -w 'W:' MAINTAINERS |wc -l
> > > 371
> > >
> > > We already have ~400 of them ... how's anyone looking for a todo list
> > > going to find the right one in amongst all the others (assuming a newbie
> > > with no subject predisposition simply trying to find any todo list).
> >
> > Hopefully the todo lists have "todo" or "TODO" in the URL. ;-)
>
> That may not be the case if you use a public todo list on
> rememberthemilk.com. It doesn't make sense to end multiple todo list
> names with "todo" for on site that's specifically designed to help with
> todo lists.
>
> I like the idea of a separate letter for todo lists URLs.
So do I! ;-)
Another option for URLs not containing "todo" or "TODO" is something like:
W: rememberthemilk.com (todo)
I suspect that most people would know not to include " (todo)" in
the string they fed to their browser.
Seem reasonable?
Thanx, Paul
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 23:23 ` Paul E. McKenney
@ 2010-08-30 1:40 ` Neil Brown
2010-08-30 15:19 ` Eric Van Hensbergen
0 siblings, 1 reply; 40+ messages in thread
From: Neil Brown @ 2010-08-30 1:40 UTC (permalink / raw)
To: paulmck
Cc: Sarah Sharp, James Bottomley, Joe Perches, ksummit-2010-discuss,
mingo, linux-kernel
On Thu, 26 Aug 2010 16:23:23 -0700
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> On Thu, Aug 26, 2010 at 04:00:21PM -0700, Sarah Sharp wrote:
> > On Thu, Aug 26, 2010 at 09:50:44AM -0700, Paul E. McKenney wrote:
> > > On Thu, Aug 26, 2010 at 11:25:33AM -0500, James Bottomley wrote:
> > > > On Thu, 2010-08-26 at 09:14 -0700, Paul E. McKenney wrote:
> > > > > On Thu, Aug 26, 2010 at 08:51:44AM -0700, Joe Perches wrote:
> > > > > > On Thu, 2010-08-26 at 08:45 -0700, Paul E. McKenney wrote:
> > > > > > > Since T: and L: are already taken, add U: for URL of todo list.
> > > > > > > Also add the RCU todo list to both the RCU and RCUTORTURE projects.
> > > > > >
> > > > > > Hi Paul
> > > > > >
> > > > > > I think W: already works perfectly well for this use.
> > > > > >
> > > > > > >From MAINTAINERS:
> > > > > > W: Web-page with status/info
> > > > > >
> > > > > > > @@ -4801,6 +4802,7 @@ M: Josh Triplett <josh@freedesktop.org>
> > > > > > > M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > > > > S: Supported
> > > > > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > > > >
> > > > > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > > > >
> > > > > > > F: Documentation/RCU/torture.txt
> > > > > > > F: kernel/rcutorture.c
> > > > > > >
> > > > > > > @@ -4826,6 +4828,7 @@ M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > > > > > W: http://www.rdrop.com/users/paulmck/rclock/
> > > > > > > S: Supported
> > > > > > > T: git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
> > > > > > > +U: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > > > >
> > > > > > W: http://kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> > > > >
> > > > > OK, how about the following, then?
> > > >
> > > > Got to say I really think overloading W which means web page/status
> > > > information isn't a very good idea:
> > > >
> > > > jejb@mulgrave:~/git/linux-2.6> grep -w 'W:' MAINTAINERS |wc -l
> > > > 371
> > > >
> > > > We already have ~400 of them ... how's anyone looking for a todo list
> > > > going to find the right one in amongst all the others (assuming a newbie
> > > > with no subject predisposition simply trying to find any todo list).
> > >
> > > Hopefully the todo lists have "todo" or "TODO" in the URL. ;-)
> >
> > That may not be the case if you use a public todo list on
> > rememberthemilk.com. It doesn't make sense to end multiple todo list
> > names with "todo" for on site that's specifically designed to help with
> > todo lists.
> >
> > I like the idea of a separate letter for todo lists URLs.
>
> So do I! ;-)
>
> Another option for URLs not containing "todo" or "TODO" is something like:
>
> W: rememberthemilk.com (todo)
>
> I suspect that most people would know not to include " (todo)" in
> the string they fed to their browser.
>
> Seem reasonable?
Yes as long as it is easy to machine-parse.
The idea that appeals to me is for the 'todo list' URL to be an RSS feed, and
we have some site that automagically extracts all the todo lists and creates
a todo planet. (todo.kernelplanet.org ??)
Then interested parties could subscribe to that and watch the ideas go by.
But getting a useful subset of maintainers to put a todo list in an RSS feed
feels somewhat like herding wild-cats...
NeilBrown
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-30 1:40 ` Neil Brown
@ 2010-08-30 15:19 ` Eric Van Hensbergen
0 siblings, 0 replies; 40+ messages in thread
From: Eric Van Hensbergen @ 2010-08-30 15:19 UTC (permalink / raw)
To: Neil Brown
Cc: paulmck, linux-kernel, James Bottomley, ksummit-2010-discuss,
Joe Perches, mingo
On Sun, Aug 29, 2010 at 8:40 PM, Neil Brown <neilb@suse.de> wrote:
>
> The idea that appeals to me is for the 'todo list' URL to be an RSS feed, and
> we have some site that automagically extracts all the todo lists and creates
> a todo planet. (todo.kernelplanet.org ??)
> Then interested parties could subscribe to that and watch the ideas go by.
>
> But getting a useful subset of maintainers to put a todo list in an RSS feed
> feels somewhat like herding wild-cats...
>
I think the best approach would be to start doing it and hope others
follow suit.
What would the standard template be for something like this? Would we
just stick to title, link, description?
-eric
^ permalink raw reply [flat|nested] 40+ messages in thread
* Re: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
2010-08-26 23:00 ` Sarah Sharp
2010-08-26 23:23 ` Paul E. McKenney
@ 2010-08-26 23:30 ` Joe Perches
1 sibling, 0 replies; 40+ messages in thread
From: Joe Perches @ 2010-08-26 23:30 UTC (permalink / raw)
To: Sarah Sharp
Cc: Paul E. McKenney, James Bottomley, ksummit-2010-discuss, mingo,
linux-kernel
On Thu, 26 Aug 2010, Sarah Sharp wrote:
> That may not be the case if you use a public todo list on
> rememberthemilk.com. It doesn't make sense to end multiple todo list
> names with "todo" for on site that's specifically designed to help with
> todo lists.
These are all general references to external "W:"eb links.
The right place for TODO lists is inside the kernel source tree
as a TODO file in the source tree node that has something to do.
^ permalink raw reply [flat|nested] 40+ messages in thread