From: Jiri Kosina <jkosina@suse.com>
To: Greg KH <greg@kroah.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] services needed from kernel.org infrastructure
Date: Wed, 8 Jul 2015 10:02:36 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1507080957360.10183@pobox.suse.cz> (raw)
In-Reply-To: <20150708021619.GC3102@kroah.com>
On Tue, 7 Jul 2015, Greg KH wrote:
> > > Those are useful, I know Greg has one and I just wrote one too. I'm not
> > > sure it needs to be on the server side though, they can also be done
> > > from the client which lets you try to fine tune things more readily.
> >
> > If either of you could share the scripts that would be great.
>
> Mine is based on Andrew's scripts, and can be found buried in my
> "gregkh-linux" repo which is a shadow of my 'linux/' subdir on my
> development machines, specifically this file:
> https://github.com/gregkh/gregkh-linux/blob/master/work/do.sh
Well, I think you've nicely demonstrated the reason why I think there
should be a central machinery; perhaps as a stanard open-source project,
i.e reviewed, contributed to, and shared by everybody.
The "everybody has his home-brew hacked-up script" model is just
unnecessary duplication of work a brings potential for unnecessary bugs.
For example, please correct me if I am wrong, but I believe that if I send
you a patch that would have authorship
Jiri Kosina <jkosina`rm -rf .`@suse.com>
and you wouldn't notice prior to applying it using the above do.sh, I
think your precious tree is gone.
This would be caught immediately if it's properly maintained "project".
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2015-07-08 8:02 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 [this message]
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
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=alpine.LNX.2.00.1507080957360.10183@pobox.suse.cz \
--to=jkosina@suse.com \
--cc=greg@kroah.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.