workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Donnellan <ajd@linux.ibm.com>
To: Daniel Axtens <dja@axtens.net>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	workflows@vger.kernel.org
Cc: 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: Tue, 1 Oct 2019 14:50:35 +1000	[thread overview]
Message-ID: <522b803e-027e-e809-5dfa-826861344bd1@linux.ibm.com> (raw)
In-Reply-To: <87blv13yxc.fsf@dja-thinkpad.axtens.net>

On 1/10/19 5:52 am, Daniel Axtens wrote:
>> (d) Support for "maintainer views"
>>
>>      That is, by default subsystem maintainers should see patches, bug reports
>>      etc against the code maintained by them, with the possibility to extend the
>>      view to also see the other submissions.
>>
>>      [That kind of is the case in Patchwork today when patches sent to different
>>       mailing lists show up under different "projects", but the problem in there
>>       is that copies of one patch appear under multiple "projects" as different
>>       entities if sent to multiple lists.]
> 
> /me puts on pw maintainer hat
> 
> This is true, they are each individual database entries. This is largely
> because projects will often change the state of patches differently. (An
> example is a patch sent to multiple lists to collect ACKs before being
> merged.)

We really should get around to adding inter-project links for matching 
message-IDs.

-- 
Andrew Donnellan              OzLabs, ADL Canberra
ajd@linux.ibm.com             IBM Australia Limited


  reply	other threads:[~2019-10-01  4:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13  8:22 Kernel development collaboration platform wish list 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 [this message]
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
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=522b803e-027e-e809-5dfa-826861344bd1@linux.ibm.com \
    --to=ajd@linux.ibm.com \
    --cc=dja@axtens.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.org \
    --cc=jikos@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=rjw@rjwysocki.net \
    --cc=skhan@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).