From: Steven Rostedt <rostedt@goodmis.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Daniel Axtens <dja@axtens.net>,
Han-Wen Nienhuys <hanwen@google.com>,
workflows@vger.kernel.org
Subject: Re: Lyon meeting notes
Date: Sat, 2 Nov 2019 07:46:47 -0400 [thread overview]
Message-ID: <20191102074647.404a6554@grimm.local.home> (raw)
In-Reply-To: <20191101172910.x7neoilwaotj5njb@pure.paranoia.local>
On Fri, 1 Nov 2019 13:29:10 -0400
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> For the lack of a better term, I'm calling it "local patchwork", though
> it's more likely to be a closely related spin-off that would hopefully
> share a lot of code with patchwork and be able to both benefit from
> upstream and to commit code back up for any shared functionality.
I know this was one of the "not within 6 months" parts, but I don't
want this to be lost.
One of the issues with a 'local patchwork' that was brought up is if
you have multiple maintainers of a single subsystem. How one maintainer
might say "accept" and another might say "reject", if one was doing
this offline, and uploaded to the central system, it could conflict
with the changes there.
What I suggested was, for multi maintainer systems, to allow for
individual accounts. Where a "accept" of a patch would require an
accept from all the given maintainers. Kind of like a hierarchy. This
way, even if you are offline, you can upload your own "accept" and it
wont affect the "reject" from the other maintainer. But you would be
able to see everyone's judgment of a patch when you get back online.
-- Steve
next prev parent reply other threads:[~2019-11-02 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 15:41 Lyon meeting notes Han-Wen Nienhuys
2019-10-29 22:26 ` Eric Wong
2019-10-29 23:13 ` Bjorn Helgaas
2019-11-01 20:07 ` Konstantin Ryabitsev
2019-11-01 20:46 ` Geert Uytterhoeven
2019-11-01 21:30 ` Theodore Y. Ts'o
2019-11-02 1:17 ` Eric Wong
2019-11-01 21:34 ` Dmitry Vyukov
2019-10-29 22:35 ` Daniel Axtens
2019-11-01 17:29 ` Konstantin Ryabitsev
2019-11-01 17:35 ` Dmitry Vyukov
2019-11-02 11:46 ` Steven Rostedt [this message]
2019-10-30 9:21 ` Jonathan Corbet
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=20191102074647.404a6554@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=dja@axtens.net \
--cc=hanwen@google.com \
--cc=konstantin@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).