From: Steven Rostedt <rostedt@goodmis.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 11:42:39 -0400 [thread overview]
Message-ID: <20150708114239.24eb3326@gandalf.local.home> (raw)
In-Reply-To: <alpine.LNX.2.00.1507081704380.10183@pobox.suse.cz>
On Wed, 8 Jul 2015 17:08:50 +0200 (CEST)
Jiri Kosina <jkosina@suse.com> wrote:
> Yes, my main point really was that I personally would find it super-nice
> to just mark particular branches in my kernel.org repositories as "send
> notifications for these", and author (and anyone else in "-by:" lines)
> would automatically receive nice notification once commit appears there.
> Without any need of wrapping simple git-am + git push with more and more
> bloated scripting.
What about the opposite. Have people subscribe to git repos and get
emails when a patch they authored is pushed to it.
I subscribe to Linus's tree, but I get all commits. I just have a
filter that only sends me anything that has my SoB, and the rest goes
to /dev/null. But it does make my fetchmail waste a lot of time pulling
in emails that mostly get discarded. It would be nice to only see those
that I'm interested in.
I wouldn't expect a korg to parse the tags, but perhaps it could just
send people emails that they authored, and want a reply to.
Note, if you are worried about security, this could all be done on an
isolated machine that doesn't have any inside access to korg itself. As
it only needs to do a git pull and parse the content. Any mischievous
scripts would only get access to a box that has nothing but a dummy
user account and a bunch of git repos that it pulls in but never
pushes, and also a way to send emails.
-- Steve
next prev parent reply other threads:[~2015-07-08 16:01 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 [this message]
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
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=20150708114239.24eb3326@gandalf.local.home \
--to=rostedt@goodmis.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.