From: Joe Perches <joe@perches.com>
To: Mark Brown <broonie@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
hpa@zytor.com, alan@linux.intel.com, acme@redhat.com,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
peterz@infradead.org, paulmck@linux.vnet.ibm.com,
akpm@linux-foundation.org, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/urgent] MAINTAINERS: Restore "L: linux-kernel@vger.kernel.org" entries
Date: Wed, 22 Jan 2014 10:18:21 -0800 [thread overview]
Message-ID: <1390414701.31946.73.camel@joe-AO722> (raw)
In-Reply-To: <20140122180643.GP17314@sirena.org.uk>
On Wed, 2014-01-22 at 18:06 +0000, Mark Brown wrote:
> On Wed, Jan 22, 2014 at 09:30:23AM -0800, Joe Perches wrote:
> > Perhaps the biggest benefit of cc'ing lkml is
> > a centralized repository of proposed patches in
> > https://patchwork.kernel.org/project/LKML/list/
>
> Which isn't triumphantly usable as a result.
True, the current search mechanism isn't ideal as it
seems to only search titles and the robots.txt file
there doesn't allow spidering.
Anyway I do think having the ability to search for
previously proposed patches to a particular file in a
single place useful but not absolutely mandatory.
cheers, Joe
next prev parent reply other threads:[~2014-01-22 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 15:49 tip-bot for Ingo Molnar
2014-01-21 17:24 ` Joe Perches
2014-01-22 12:27 ` Ingo Molnar
2014-01-22 13:02 ` Joe Perches
2014-01-22 16:09 ` Mark Brown
2014-01-22 17:30 ` Joe Perches
2014-01-22 18:06 ` Mark Brown
2014-01-22 18:18 ` Joe Perches [this message]
2014-01-22 17:36 ` Ingo Molnar
2014-01-22 17:47 ` Joe Perches
2014-01-22 12:27 tip-bot for Ingo Molnar
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=1390414701.31946.73.camel@joe-AO722 \
--to=joe@perches.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=broonie@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®