On Tue, 2010-08-31 at 16:25 -0700, Luck, Tony wrote:
quoted text
> >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


--
unsubscribe notice
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/