From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jiri Kosina <jkosina@suse.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] services needed from kernel.org infrastructure
Date: Wed, 8 Jul 2015 09:25:06 -0400 [thread overview]
Message-ID: <20150708132506.GA14279@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1507071324090.10183@pobox.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
On Tue, Jul 07, 2015 at 10:42:49PM +0200, Jiri Kosina 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.
I suggest people just email users@linux.kernel.org. :) I've always
solicited such conversations, but in my previous experience these tend
to fall into two categories:
1. "Here's a minor suggestion that could be kinda cool, whenever you
have some time."
2. "Here's a radical idea that would require a park of 1,000 various
hardware systems and a dedicated staff of 10 people."
There doesn't appear to be a lot that falls between these two
categories. This is not to say that #2 is not possible, it's just that
we have to operate within LF budget constraints and people never tend to
follow such grand requests with "and here's my $EMPLOYER who's happy to
fund this initiative." If you do happen to be in such a position, then
I'll be happy to get you in touch with the Collab Projects management
team.
> 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.
We have the following script running on torvalds/linux.git:
http://ur1.ca/n2iof
It has two downsides:
1. It sends an email per each commit, which tends to thrash the lists
(e.g. see https://marc.info/?l=git-commits-head where Linus's tree goes)
2. It doesn't fork into background while doing that, so you have to wait
for it to finish sending the emails.
If that's fine with you all, I can enable this for other repos as well.
All I'd need would be the destination list address.
> Suggested attendance: Konstantin, maintainers :)
I'll be at the summit.
Best,
--
Konstantin Ryabitsev
Linux Foundation Collab Projects
Montréal, Québec
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-07-08 13:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 20:42 [Ksummit-discuss] [CORE TOPIC] services needed from kernel.org infrastructure 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
2015-07-08 8:01 ` Geert Uytterhoeven
2015-07-08 7:31 ` James Bottomley
2015-07-08 13:25 ` Konstantin Ryabitsev [this message]
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=20150708132506.GA14279@gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=jkosina@suse.com \
--cc=ksummit-discuss@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.