mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type
Date: Thu, 14 Jan 2010 20:05:00 +0100	[thread overview]
Message-ID: <4B4F6ADC.7090501@s5r6.in-berlin.de> (raw)
In-Reply-To: <1263494720.1903.21.camel@Joe-Laptop.home>

Joe Perches wrote:
> On Thu, 2010-01-14 at 19:34 +0100, Stefan Richter wrote:
>> MAINTAINERS' MIPS entry links to http://www.linux-mips.org/
>> which in turn points MIPS platform developers to
>> http://patchwork.linux-mips.org/.  So that's already been taken care of.
> 
> www.google.com gives an easy interface to search for links.
> How about we remove all other links in kernel sources?

www.google.com is a rather unreliable tool to obtain patch submission
addresses.  Hence the MAINTAINERS database.  This database is especially
useful to first-timers and to those who submit patches across the tree
or to subsystems with which they normally don't work with.

Patchwork listings OTOH are more interesting to those who work with
particular subsystems on a more regular basis.  Hence there is lesser
need to have the same kind of database for them as for the patch
submission addresses.

Nevertheless, rather exhaustive and always up-to-date listings of
patchwork links already exist at http://patchwork.kernel.org/ and
http://patchwork.ozlabs.org/.  As was pointed out, one or another
subsystem may have a patchwork tracker on another site, but this alone
is not a reason to add and _maintain_ a huge list of patchwork links in
the MAINTAINERS file.

Your proposal to add those links into MAINTAINERS does not duplicate
Google, it duplicates the entry pages of http://patchwork.kernel.org/
and http://patchwork.ozlabs.org/.

And again, the W: entries in MAINTAINERS are an effective way to have
auxiliary information accessible from MAINTAINERS --- indirectly, but
tailored to the needs of each subsystem group, with the possibility to
add arbitrary depth of information, and potentially more up-to-date than
MAINTAINERS.
-- 
Stefan Richter
-=====-==-=- ---= -===-
http://arcgraph.de/sr/

  reply	other threads:[~2010-01-14 19:05 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14  7:12 [PATCH 00/24] MAINTAINERS: Add "Q" patchwork entries Joe Perches
2010-01-14  7:13 ` [PATCH 01/24] MAINTAINERS: Document new "Q:" patchwork queue type Joe Perches
2010-01-14 13:48   ` Stefan Richter
2010-01-14 14:02     ` Stefan Richter
2010-01-14 17:38       ` Joe Perches
2010-01-14 18:04         ` Stefan Richter
2010-01-14 18:13           ` Joe Perches
2010-01-14 18:34             ` Stefan Richter
2010-01-14 18:45               ` Joe Perches
2010-01-14 19:05                 ` Stefan Richter [this message]
2010-01-14 19:05                 ` Alan Cox
2010-01-14 19:13                   ` Joe Perches
2010-01-14 19:39                     ` Stefan Richter
2010-01-14 21:05                       ` Joe Perches
2010-01-14 22:39                         ` [PATCH] HOWTO: Updates on subsystem trees, patchwork, -next (vs. -mm) Stefan Richter
2010-01-14 23:36                           ` Randy Dunlap
2010-01-15  0:41                           ` Loïc Grenié
2010-01-15 12:23                             ` [PATCH update] " Stefan Richter
2010-01-18  8:25                               ` Stephen Rothwell
2010-01-18 14:26                           ` [PATCH] " Valdis.Kletnieks
2010-01-18 15:19                             ` Stefan Richter
2010-01-14 18:20           ` [PATCH] HOWTO: Point to patchwork.kernel.org and patchwork.ozlabs.org Stefan Richter
2010-01-14  7:13 ` [PATCH 02/24] MAINTAINERS: 9P FILE SYSTEM - Add "Q" patchwork entry Joe Perches
2010-01-14  7:13 ` [PATCH 03/24] MAINTAINERS: ACPI " Joe Perches
2010-01-14  7:13 ` [PATCH 04/24] MAINTAINERS: BTRFS FILE SYSTEM " Joe Perches
2010-01-14  7:13 ` [PATCH 05/24] MAINTAINERS: CIFS " Joe Perches
2010-01-14  7:13 ` [PATCH 06/24] MAINTAINERS: DEVICE-MAPPER " Joe Perches
2010-01-14  7:13 ` [PATCH 07/24] MAINTAINERS: EXT4 FILE SYSTEM " Joe Perches
2010-01-14 20:27   ` tytso
2010-01-14  7:13 ` [PATCH 08/24] MAINTAINERS: IDE SUBSYSTEM " Joe Perches
2010-01-14  7:13 ` [PATCH 09/24] MAINTAINERS: INFINIBAND " Joe Perches
2010-01-14  7:13 ` [PATCH 10/24] MAINTAINERS: INPUT DRIVERS " Joe Perches
2010-01-14  7:13 ` [PATCH 11/24] MAINTAINERS: KCONFIG " Joe Perches
2010-01-14  7:13 ` [PATCH 12/24] MAINTAINERS: LINUX FOR POWERPC " Joe Perches
2010-01-14  7:13 ` [PATCH 13/24] MAINTAINERS: V4L/DVB " Joe Perches
2010-01-14  7:13 ` [PATCH 14/24] MAINTAINERS: MTD " Joe Perches
2010-01-14  7:13 ` [PATCH 15/24] MAINTAINERS: NETWORKING [WIRELESS] " Joe Perches
2010-01-14  7:13 ` [PATCH 16/24] MAINTAINERS: OMAP " Joe Perches
2010-01-19 18:11   ` Tony Lindgren
2010-01-14  7:13 ` [PATCH 17/24] MAINTAINERS: PARISC ARCHITECTURE " Joe Perches
2010-01-14  7:13 ` [PATCH 18/24] MAINTAINERS: PCI SUBSYSTEM " Joe Perches
2010-01-14  7:13 ` [PATCH 19/24] MAINTAINERS: REAL TIME CLOCK " Joe Perches
2010-01-14  7:13 ` [PATCH 20/24] MAINTAINERS: TI DAVINCI " Joe Perches
2010-01-14  7:13 ` [PATCH 21/24] MAINTAINERS: SPARC " Joe Perches
2010-01-14  7:13 ` [PATCH 22/24] MAINTAINERS: SPI SUBSYSTEM " Joe Perches
2010-01-14 13:38   ` Grant Likely
2010-01-14  7:13 ` [PATCH 23/24] MAINTAINERS: SUPERH " Joe Perches
2010-01-14  7:13 ` [PATCH 24/24] MAINTAINERS: THE REST (LKML) " Joe Perches
2010-01-14 17:24 ` [PATCH 00/24] MAINTAINERS: Add "Q" patchwork entries David Daney
2010-01-14 17:40   ` Joe Perches

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=4B4F6ADC.7090501@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome