From: Joe Perches <joe@perches.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
"ksummit-2010-discuss@lists.linux-foundation.org"
<ksummit-2010-discuss@lists.linux-foundation.org>,
"mingo@elte.hu" <mingo@elte.hu>
Subject: RE: [Ksummit-2010-discuss] [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
Date: Tue, 31 Aug 2010 16:46:31 -0700 [thread overview]
Message-ID: <1283298391.1797.100.camel@Joe-Laptop> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D53015D9B2445@orsmsx505.amr.corp.intel.com>
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
next prev parent reply other threads:[~2010-08-31 23:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 15:45 [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list 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
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 [this message]
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=1283298391.1797.100.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ksummit-2010-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tony.luck@intel.com \
/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