From: Joe Perches <joe@perches.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, jkosina@suse.cz,
ksummit-2010-discuss@lists.linux-foundation.org
Subject: Re: [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list
Date: Thu, 26 Aug 2010 08:51:44 -0700 [thread overview]
Message-ID: <1282837904.1875.64.camel@Joe-Laptop> (raw)
In-Reply-To: <20100826154537.GA4874@linux.vnet.ibm.com>
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
next prev parent reply other threads:[~2010-08-26 15:51 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 ` Joe Perches [this message]
2010-08-26 16:14 ` [PATCH] MAINTAINERS: add U: for URL of todo list, add RCU todo list 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
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=1282837904.1875.64.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=jkosina@suse.cz \
--cc=ksummit-2010-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.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