ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] services needed from kernel.org infrastructure
Date: Tue, 7 Jul 2015 16:38:55 -0700	[thread overview]
Message-ID: <CALCETrVxt5xZ+ewoOR8TVH7YgN4mJkahVXSep2-aGoX4_i7mOQ@mail.gmail.com> (raw)
In-Reply-To: <559C62D0.9090301@roeck-us.net>

On Tue, Jul 7, 2015 at 4:37 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On 07/07/2015 04:31 PM, Andy Lutomirski wrote:
>>
>> On Tue, Jul 7, 2015 at 1:42 PM, Jiri Kosina <jkosina@suse.com> wrote:
>>>
>>> I think it'd be useful to have a session where maintainers could come up
>>> with feature / improvement requests for kernel.org infrastructure and
>>> have
>>> a subsequent discussion about whether they would be generally useful.
>>>
>>> Let me start with my personal wish:
>>>
>>> I personally would very welcome a facility that'd send out an e-mail if a
>>> new commit is pushed to a git.kernel.org repo branch (sort of what
>>> tip-bot
>>> and akpm's scripts are doing these days) to automatically notify the
>>> patch
>>> author that the patch has been merged and pushed out.
>>>
>>> Suggested attendance: Konstantin, maintainers :)
>>
>>
>> I wouldn't mind something like patchwork for lkml.  Since I use gmail
>> (sigh), it's a minor PITA to pull out patchbombs in git am-able
>> format.
>>
> What is wrong with https://patchwork.kernel.org/project/LKML/list/ ?

It's not spelled "linux-kernel".

/me runs away

--Andy

  reply	other threads:[~2015-07-07 23:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 20:42 Jiri Kosina
2015-07-07 22:40 ` Mark Brown
2015-07-07 22:52   ` Dmitry Torokhov
2015-07-08  2:16     ` Greg KH
2015-07-08  8:02       ` Jiri Kosina
2015-07-08  9:35         ` Mark Brown
2015-07-08 14:01           ` Theodore Ts'o
2015-07-08 14:36             ` Jason Cooper
2015-07-08 14:40             ` Jiri Kosina
2015-07-08 15:00             ` Greg KH
2015-07-12 12:55             ` Fengguang Wu
2015-07-13 16:22               ` Steven Rostedt
2015-07-14 13:07                 ` Fengguang Wu
2015-07-08 14:59         ` Greg KH
2015-07-08 15:08           ` Jiri Kosina
2015-07-08 15:42             ` Steven Rostedt
2015-07-07 22:53   ` josh
2015-07-08  7:35   ` Jiri Kosina
2015-07-08 13:05   ` Jason Cooper
2015-07-07 23:31 ` Andy Lutomirski
2015-07-07 23:37   ` Guenter Roeck
2015-07-07 23:38     ` Andy Lutomirski [this message]
2015-07-08  8:01   ` Geert Uytterhoeven
2015-07-08  7:31 ` James Bottomley
2015-07-08 13:25 ` Konstantin Ryabitsev

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=CALCETrVxt5xZ+ewoOR8TVH7YgN4mJkahVXSep2-aGoX4_i7mOQ@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux@roeck-us.net \
    /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