From: Shuah Khan <skhan@linuxfoundation.org>
To: Bjorn Helgaas <helgaas@kernel.org>, "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Topics for the Maintainer's Summit
Date: Mon, 2 Sep 2019 09:09:46 -0600 [thread overview]
Message-ID: <0bdf3e0e-e352-8cac-5c38-fd6086681e8e@linuxfoundation.org> (raw)
In-Reply-To: <20190830135857.GF7013@google.com>
On 8/30/19 7:58 AM, Bjorn Helgaas wrote:
> On Thu, Aug 29, 2019 at 11:17:20PM -0400, Theodore Y. Ts'o wrote:
>> ...
>> Are there some additional topics that you'd like to suggest that we
>> discuss at the maintainer's summit?
>
> I don't have an effective workflow for managing incoming patches. I
> use a hodge-podge of patchwork, gmail, mutt, and ugly private scripts
> to put patches on topic branches, review them, polish them, merge them
> together into a "-next" branch, generate pull requests, etc.
>
> I wish there were a collection of the workflows and scripts people
> use, maybe even in the kernel sources so they could be shared and
> improved. Some short screencasts could help visualize and pull things
> together. I know a lot of this stuff is "out there" somewhere, but
> I'm not aware of any organized collection.
>
This is a great idea. Folds in to my request make the script that pulls
in the Link tag widely available.
Patch version changes in commit logs? (Shuah Kahn)
How to make information about how commit has changed while being
developed. (A solution which has already been adopted by some
maintainers is to use the Link: tag in the commit discussion).
There have been a more recent discussion in this past week under
subject line "Allowing something Change-Id (or something like it)
in kernel commits".
I have a work-flow that works and I would like to learn from others and
improve mine.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-09-02 15:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 3:17 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 [this message]
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
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=0bdf3e0e-e352-8cac-5c38-fd6086681e8e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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