From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Laura Abbott <labbott@redhat.com>,
Bjorn Helgaas <helgaas@kernel.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Topics for the Maintainer's Summit
Date: Tue, 3 Sep 2019 11:14:46 -0700 [thread overview]
Message-ID: <CAPcyv4gMAMG6ejwjyzVahE0hGLyf7Rcq+7QZ-SzYsvFW65YdVA@mail.gmail.com> (raw)
In-Reply-To: <20190903172708.qrvaad2paze6ifhz@chatter.i7.local>
On Tue, Sep 3, 2019 at 10:27 AM Konstantin Ryabitsev
<konstantin@linuxfoundation.org>
[..]
> So:
>
> - would a tool with such functionality be useful, or would every
> maintainer prefer to continue doing their own thing (in slightly
> different ways)?
Yes, I would consider switching to this. The kernel.org patchwork-bot
+ the getpatchwork tool [1] does some of this for me, but lossless
patch reception, sharing rules and triggers for patches (not just
git-hooks) is a powerful superset.
[1]: https://github.com/getpatchwork/git-pw
next prev parent reply other threads:[~2019-09-03 18:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 3:17 [Ksummit-discuss] Topics for the Maintainer's Summit Theodore Y. Ts'o
2019-08-30 12:01 ` Wolfram Sang
2019-08-30 13:58 ` Shuah Khan
2019-08-30 14:36 ` shuah
2019-08-30 13:58 ` Bjorn Helgaas
2019-09-02 15:09 ` Shuah Khan
2019-09-02 20:42 ` Dave Airlie
2019-09-02 22:22 ` Theodore Y. Ts'o
2019-09-03 2:35 ` Olof Johansson
2019-09-03 3:05 ` Randy Dunlap
2019-09-03 13:29 ` Laura Abbott
2019-09-03 16:07 ` Linus Torvalds
2019-09-03 17:27 ` Konstantin Ryabitsev
2019-09-03 17:40 ` Bjorn Helgaas
2019-09-06 10:21 ` Rob Herring
2019-09-19 1:47 ` Bjorn Helgaas
2019-09-19 20:52 ` Rob Herring
2019-09-20 13:37 ` Mark Brown
2019-09-03 17:57 ` Mark Brown
2019-09-03 18:14 ` Dan Williams [this message]
2019-09-03 21:59 ` Wolfram Sang
2019-09-04 8:34 ` Jan Kara
2019-09-04 12:08 ` Laurent Pinchart
2019-09-04 13:47 ` Konstantin Ryabitsev
2019-09-05 8:21 ` Jani Nikula
2019-09-06 10:50 ` Rob Herring
2019-09-06 19:21 ` Linus Torvalds
2019-09-06 19:53 ` Olof Johansson
2019-09-09 8:40 ` Jani Nikula
2019-09-09 9:49 ` Geert Uytterhoeven
2019-09-09 10:16 ` Konstantin Ryabitsev
2019-09-09 10:59 ` Geert Uytterhoeven
2019-09-09 12:37 ` Konstantin Ryabitsev
[not found] ` <20190911095305.36104206A1@mail.kernel.org>
2019-09-11 11:03 ` Christoph Hellwig
2019-09-13 8:19 ` Matthias Brugger
2019-09-05 7:01 ` Jani Nikula
2019-09-05 15:26 ` Theodore Y. Ts'o
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=CAPcyv4gMAMG6ejwjyzVahE0hGLyf7Rcq+7QZ-SzYsvFW65YdVA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=helgaas@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).