From: Dmitry Vyukov <dvyukov@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
workflows@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Jiri Kosina <jikos@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Kernel development collaboration platform wish list
Date: Sun, 29 Sep 2019 18:03:00 +0200 [thread overview]
Message-ID: <CACT4Y+ZpP0d+bSGQRZSu-FJuQzHtrSnh+R29Py-rABe6U1D8Jw@mail.gmail.com> (raw)
In-Reply-To: <20190928181615.581ea87d@oasis.local.home>
On Sun, Sep 29, 2019 at 12:16 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Thu, 26 Sep 2019 15:39:54 +0200
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> > On Thu, Sep 26, 2019 at 3:02 PM Steven Rostedt <rostedt@goodmis.org> wrote:
> > > That would be wonderful.
> >
> > Oh, the irony ;-)
> >
>
> Sorry, I couldn't resist ;-)
>
> -- Steve
>
> > > -- Steve
> > >
> > > On September 26, 2019 12:18:18 PM GMT+02:00, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >
> > [...]
> >
> > > >And if it's done right, it may solve (or make it harder to show) other
> > > >bad review
> > > >behavior, like:
> > > > - Top posting review comments,
> > > >- Quoting a 2000-line patch when commenting on a single line deep down.
Hi,
I've aggregated the requirements that people mentioned so far here:
https://github.com/dvyukov/kit/blob/master/doc/references.md
I think we need some centralized docs related to this effort.
Information scattered across multiple long email threads and some
private discussions won't be manageable. In future we can extend and
refine the list, put more structure (e.g. v1 vs v2 requirements), etc.
Also references to other development support systems:
https://github.com/dvyukov/kit/blob/master/doc/requirements.md
(people keep mentioning more and more, I've found some interesting
ones e.g. git-appraise, so I thought it would be good to collect the
list)
Why is this on my private github? It was just easier to put an initial
version there. If there is a better shared place, I am happy to move
this.
next prev parent reply other threads:[~2019-09-29 16:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 8:22 Rafael J. Wysocki
2019-09-13 11:13 ` Jani Nikula
2019-09-17 21:58 ` Rafael J. Wysocki
2019-09-18 8:05 ` Jani Nikula
2019-09-18 13:43 ` Steven Rostedt
2019-09-13 11:37 ` Laurent Pinchart
2019-09-13 12:02 ` Geert Uytterhoeven
2019-09-13 12:15 ` Laurent Pinchart
2019-09-13 12:23 ` Geert Uytterhoeven
2019-09-17 22:00 ` Rafael J. Wysocki
2019-10-02 9:30 ` Rafael J. Wysocki
2019-09-17 18:40 ` Stefan Schmidt
2019-09-24 9:43 ` Paolo Bonzini
2019-09-24 12:20 ` Stefan Schmidt
2019-09-17 22:12 ` Rafael J. Wysocki
2019-10-01 3:52 ` Daniel Axtens
2019-10-01 4:50 ` Andrew Donnellan
2019-10-01 5:04 ` Daniel Axtens
2019-09-23 16:20 ` Theodore Y. Ts'o
2019-09-24 1:39 ` Eric Wong
2019-09-24 5:06 ` Greg Kroah-Hartman
2019-10-01 3:58 ` Daniel Axtens
2019-09-26 10:18 ` Geert Uytterhoeven
2019-09-26 11:40 ` Steven Rostedt
2019-09-26 13:39 ` Geert Uytterhoeven
2019-09-28 22:16 ` Steven Rostedt
2019-09-29 16:03 ` Dmitry Vyukov [this message]
2019-09-26 13:10 ` Jani Nikula
2019-09-26 13:41 ` Geert Uytterhoeven
2019-09-26 14:40 ` Jani Nikula
2019-10-02 9:55 ` Rafael J. Wysocki
2019-10-02 14:22 ` Daniel Axtens
2019-10-03 9:23 ` Rafael J. Wysocki
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=CACT4Y+ZpP0d+bSGQRZSu-FJuQzHtrSnh+R29Py-rABe6U1D8Jw@mail.gmail.com \
--to=dvyukov@google.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=jikos@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
--cc=workflows@vger.kernel.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